Community
Participate
Working Groups
Build Identifier: 3.1, 3.6 The HTML tag in Eclipse created pages does not contain a language tag and fails W3C guidelines for accessibility. If those tags are generated by IDWB and transformed into an Eclipse TOC, those tags are hidden in the frame where the content resides, but the TOC retains an inaccessible HTML tag without lang attributes and fails W3C guidelines. Reproducible: Always Steps to Reproduce: 1. Open an Eclipse built page 2. View page source. The first HTNL tag will look like this: <html>. It makes the whole page inaccessible. 3. View frame source in the content frame. It may look like this: <html xmlns="http://www.w3.org/1999/xhtml" lang="en-us" xml:lang="en-us">.
It violates W3c guidline 3.1a
The HTML lang tag violates 3.1a But, a similar problem violates 2.4b <div role="main"><!-- --></div><h1 class="title topictitle1"> and 4.1a <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" All of these necessary tags and labels are hidden in the content frame and not repeated at the top of the page. It causes accessibility violations in all cases.
(In reply to comment #0) > 1. Open an Eclipse built page Did you mean "build"? Please provide a link.
Please provide a link to the page. PW
I opened the bug in response to this internal IBM page: https://idoc2.swg.usma.ibm.com/lotuslive/index.jsp?topic=/com.ibm.lotuslive.activities.doc/w_oa_c_entries.html
In current Eclipse 4.2 code, the top level page (index.jsp) starts like this: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> <!------------------------------------------------------------------------------ ! Copyright (c) 2000, 2007 IBM Corporation and others. ! All rights reserved. This program and the accompanying materials ! are made available under the terms of the Eclipse Public License v1.0 ! which accompanies this distribution, and is available at ! http://www.eclipse.org/legal/epl-v10.html ! ! Contributors: ! IBM Corporation - initial API and implementation -------------------------------------------------------------------------------> <html lang="en"> This is better than previous versions that start with just <html> (ie, no 'lang' attribute). Is that sufficient to make the page accessible or are the other tags (like xml:lang) also required?
(In reply to Steve Francisco from comment #6) > In current Eclipse 4.2 code, the top level page (index.jsp) starts like this: > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> > <!--------------------------------------------------------------------------- > --- > ! Copyright (c) 2000, 2007 IBM Corporation and others. > ! All rights reserved. This program and the accompanying materials > ! are made available under the terms of the Eclipse Public License v1.0 > ! which accompanies this distribution, and is available at > ! http://www.eclipse.org/legal/epl-v10.html > ! > ! Contributors: > ! IBM Corporation - initial API and implementation > ---------------------------------------------------------------------------- > ---> > <html lang="en"> > > This is better than previous versions that start with just <html> (ie, no > 'lang' attribute). Is that sufficient to make the page accessible or are > the other tags (like xml:lang) also required? : Steve, the bug is about html pages generated by RAP. This bug is a blocker to passing web accessibility checklist/guidelines. Are there any plans to have it fixed?
(In reply to Barys Dubauski from comment #7) > > <html lang="en"> > > > > This is better than previous versions that start with just <html> (ie, no > > 'lang' attribute). Is that sufficient to make the page accessible or are > > the other tags (like xml:lang) also required? > : > Steve, the bug is about html pages generated by RAP. This bug is a blocker > to passing web accessibility checklist/guidelines. Are there any plans to > have it fixed? If you are talking about web pages generated by RAP, they do not belong in this bug. Please open a bug against RAP. PW
Oops, you are correct Paul. I didn't notice that this one was filed against Platform and not RAP product. I'll open a separate one for RAP.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the stalebug whiteboard tag.
