Closed
Bug 1119733
Opened 10 years ago
Closed 10 years ago
Breakdown: file bugs for sec508 report issues identified
Categories
(Firefox :: Disability Access, defect)
Firefox
Disability Access
Tracking
()
RESOLVED
FIXED
Iteration:
38.1 - 26 Jan
People
(Reporter: Gijs, Assigned: Gijs)
References
(Depends on 6 open bugs)
Details
(Keywords: access)
Attachments
(1 file)
(deleted),
application/pdf
|
Details |
There was an "initial test for Mozilla Firefox for Microsoft Windows 7 software using the DHS Section 508 Compliance Test Process for Applications".
I'm marking OS/arch as all/all because many of the issues identified apply everywhere, not just on Windows (7).
I'll be going through the report and filing bugs where they haven't been already, starting sometime next week.
David, any reason not to attach the report here?
Flags: qe-verify-
Flags: needinfo?(dbolter)
Flags: in-testsuite-
Flags: firefox-backlog+
Updated•10 years ago
|
Iteration: 37.3 - 12 Jan → 38.1 - 26 Jan
Assignee | ||
Comment 2•10 years ago
|
||
Assignee | ||
Comment 3•10 years ago
|
||
I've not filed a bug about the colors section of the content dialog. This does use only color for a UI indication - namely what color will be used for different elements on the screen. I think that is sensible; the typical reason not to have color-only information is because if they represent warnings or states, they are not accessible to people with various types of alternative-color-vision ("colorblindness"). However, in this case, the colors represent only themselves (that is, the colors used as foreground/background/link colors) not some other semantic bit of information, so I don't think this is an issue per sec508/wcag.
With that, I think the deps now cover all the issues that were identified, so I'm closing this. Norman/David, please let me know and/or reopen if you think I've missed something.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 4•10 years ago
|
||
CC'ing a more up-to-date email address for Norman in case he has comments. :-)
You need to log in
before you can comment on or make changes to this bug.
Description
•