Closed Bug 1419635 Opened 7 years ago Closed 7 years ago

In the MDN learning area of "HTML - Structuring the web" > "HTML tables" > "HTML table advanced features and accessibility", the answer for the "Active learning: playing with scope and headers" has three mistakes.

Categories

(Developer Documentation Graveyard :: Learning Area, enhancement, P1)

All
Other
enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: thomas.anderson, Assigned: cmills)

Details

(Whiteboard: [specification][type:bug])

What did you do? ================ 1. I completed the exercise. 2. I tested my answer visually. 3. I downloaded the MDN answer at https://github.com/mdn/learning-area/blob/master/html/tables/advanced/items-sold-headers.html 4. I compared the MDN answer to mine and found 3 mistakes in the MDN answer: a. Line 53 has "blegium" instead of "belgium". b. Line 61 has "clothers" instead of "clothes". c. Line 68 is using a "headers" attribute instead of an "id" attribute. What happened? ============== N/A What should have happened? ========================== N/A Is there anything else we should know? ====================================== No, nothing additional you should know. However I'm curious if there is a decent freeware screen reader that I can play with to test how it works and to check if my web pages are fairly readable and understandable via the screen reader, since the "scope", "id", and "header" attributes don't seem to impact the visual version of the web page. Do you have any suggestions?
Those are the kind of changes that can be made using the GitHub webpage. You can sign in to GitHub and click the "pencil" icon to make your changes and open a pull request. Here's a couple of pages that answer your follow-on question: https://stackoverflow.com/questions/796887/screen-readers-for-testing-website-accessibility https://stackoverflow.com/questions/2323683/which-screen-reader-would-be-best-to-test-site-accessibility-and-how-to-configur
Status: UNCONFIRMED → NEW
Component: General → Learning Area
Ever confirmed: true
Product: Mozilla Developer Network → Developer Documentation
Priority: -- → P1
I've made these fixes. In terms of screenreaders, VoiceOver is great if you're on a Mac (built-in), NVDA is good if you're on Windows/Linux, Orca is good for Linux. See here for a useful guide: https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Cross_browser_testing/Accessibility#Screenreaders
Assignee: nobody → cmills
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.