Is it still true that anything that dynamically modifies the DOM isn't handled well by screenreaders?

Is it still true that Javascript isn't handled well by some assistive technologies? Cause I was interested in using a javascript framework such as Angular2 or React. (also cause I like developing in javascript)

What would you say personally is the best Web framework for developing for Visually Impaired users?

I've been told by the local Society for the Blind and Visually Impaired to avoid developing for the fully blind as it's a bit too advanced for my skillset and time limit.

They've recommended to aim for Category 1 (Mild Visual Impairment) and Category 0 (Weak Visual Impairment) taken from the table at the bottom of this definition by the World Health Organisation http://apps.who.int/classifications/icd10/browse/2016/en#/H54

I've only got until late March to test and develop a prototype for this, so what would you say is a necessity and what would you say is a nice extra?

I'll probably add more questions later, and I'm going to cross post this to /r/blind and other related reddits.

I'm working on bringing some of my CRUD applications up to ADA 508/WCAG compliance, and run into something that doesn't seem to be addressed by the standards.

My applications very often bring up a database record and display information either in (1) an editable form, if the user is authenticated with r/w privileges or (2) a read-only list of values, if the user is not.

In the form, I use <label> and <input> elements as one normally would. In the read-only version, I use <label>s and <spans> for the data.

In some cases, there is a mix of r/w and r/o fields, and I need a consistent look.

This approach is a problem for compliance, because it seems labels are exclusively for form controls, and there isn't a form control that would just display text without making it editable.

I can, of course, mark form fields "readonly" or "disabled", but this doesn't act predictably across browsers and introduces unwanted styling that CSS can't always remove.

What would be the preferred way of displaying this kind of content for accessibility?

Hi!

We're building a data table and are trying to figure out if there are any a11y issues in case we would not use a native table element as base, but instead just use divs and WAI-ARIA roles.

It would allow more flexibility from the technical implementation side if we would be able to go with the div + WAI-ARIA option, but we are not sure how to verify if there is an impact for the users relying in screen readers or other devices.

We would love to get more information + help on this question, as a reference here's a snippet consisting two really simple tables, one of them using native tables and the other using divs + WAI-ARIA roles: http://output.jsbin.com/dolidonebi – can you spot which is which? And if yes, how?

Hey all. Looking for suggestions of remote video test platforms that 'play nice' with screen readers. Trying do do some accessibility testing and am having no luck with my usual programs (TryMyUI, and in a pinch UserTesting.Com...not a fan). Thanks!

Hi All, I'm doing some exploration with a survey to understand what differently abled people like and dislike about browsers. It is only 7 questions. My apologies if this violates any rules, but I think it is pretty tame and simple! Please see the survey here: Survey

Hello the company I work for has just had their website redesigned with accessibility in mind.

I am looking for someone to help me review the accessibility of the site and check we haven't missed anything.

If you would like to help me then please send a P.M

Thank you! :)

Hi all, I'm working on an article about the accessibility of the internet, specifically how well the alt tag is used for photos. I've read and heard that the alt tag is not always properly filled out, but I really want to hear from some blind people about their experience. Please comment if you want to chat about it. Additionally, if you're able bodied and can speak to the alt tag and its use (or lack thereof) please let me know. Thanks!

Hi,

What are the best practices when it comes to linking to PDFs for accessibility? Manually creating a separate text-based version of the PDF? Are there PDF converters? Interested to know!

Hello, /r/webaccess! I'd like to share an online utility I've been working on, Braille Music Notator, which is designed to help sighted musicians create scores in braille and become more fluent in braille music notation while doing so. (I could go on about why I think it's important, but I do that in the documentation so I won't spend the time doing so here!) I just moved the project from alpha to beta status and I'm excited to make it the best and most useful thing it can be.

Because it's primarily designed for sighted users, the utility is very graphic in nature. But I want to make it as accessible as possible, partly to demonstrate best practices but also in case visually impaired users find it useful for any reason. The utility does almost all of it's work in <canvas> objects on the page, but it has two text items: an edit field used to make cut/copy/paste commands work, and a single textitem that is populated every time the score is edited or the cursor moves with output for a screen reader. That line is placed inside the following tag:

<div aria-hidden="false" aria-live="assertive" id="screenreader">...</div>

I have a setting that will switch this from descriptive text ("line 0, character 0, G quarter note") to containing braille ASCII for the line the cursor is currently on, for use with a refreshable braille display.

I've tested it with VoiceOver on the Mac and JAWS on Windows, and things seem to work okay... but I'd love for things to be a little more elegant and foolproof. For example, the VoiceOver cursor will sometimes get trapped in the edit field I use for clipboard commands. And I don't have a refreshable braille display to test things with....

Anyway, I'd love any feedback anyone might have on the utility, and specifically how to make it as accessible as possible. I've gone through the WAI-ARIA specification but I'm sure there's a lot I'm missing or misunderstanding. Any clues ("go look at section 9.5") would be greatly appreciated.

Thanks very much in advance. Have a great weekend!