Blog

What am I talking about? I’m talking about using aria-modal when the application is not blocking all users. This goes against the ARIA spec. Of course I’m not in favor of offering limited software functionality to users with disabilities but in complex software it may be necessary to at least temporarily limit certain functionality for… Read more Serializing the tab order and reading order and using aria-modal in a way the spec advises against

I have the honor of presenting a webinar for IAAP – International Association of Accessibility Professionals. Please see the information below. Date: Thursday, March 28, 2019 Time: 11:00 a.m. – 12:30 p.m. Eastern (UTC – 4 hours) Speaker(s): Chris Lane, Accessibility Engineer, VMware Target Audience: Web developers working with AngularJS or ReactJS Skill Level: Beginner-Intermediate… Read more IAAP Webinar – Web Accessibility techniques for React and Angular

On 12/12/18 I gave a talk called Accessible Routing with React for the Bay Area Accessibility and Inclusive Design meetup group. I discussed the following examples of title and focus management using React. Basic routing with no title or focus management Updating the title and moving focus to the newly loaded component after routing and… Read more Speaking at the Bay Area Accessibility and Inclusive Design Meetup 12/12/18

I’ve come to the conclusion that there is only one strategy for focus management when routing in a single page application. Focus must be set to an element that meets the following requirements: The element is visible or hidden with offscreen text from http://whatsock.com/ .offscreenText { position: absolute; clip: rect(1px 1px 1px 1px); /* IE6,… Read more Title and Focus Management with Angular and React

I thought same page links would move focus from the link to the target but they don’t. They only scroll the page. See https://www.chrislane.info/examples/samePageLink2.html#target. Focus movement has to be scripted for same page links. See https://www.chrislane.info/examples/samePageLink.html#

Update: 3/1/18 I still think ARIA menus can be used for navigation. But they have to be implemented perfectly, which may not be worth the effort vs. using a bunch of standard HTML links. See https://www.levelaccess.com/challenges-mega-menus-standard-menus-make-accessible/. Some think that ARIA menus should not be used for navigation. They typically cite the following definitions from ARIA… Read more Menubars for navigation

This comment from dylanb at https://github.com/w3c/html-aria/issues/67 makes a lot of sense to me. It makes no sense to have a required attribute on a field that can only have unchecked and checked IF both values (unchecked and checked) are allowable. What is being required? For a radio button grouping, the “required” attribute applies to the group and… Read more aria-required doesn’t make sense on radio buttons, maybe checkboxes

The WebAIM Screen Reader Survey 7 results are out. Firefox usage surpassed IE for the first time. But JAWS and IE are still the most popular screen reader and browser combination. http://www.webaim.org/projects/screenreadersurvey7

  While testing and Android app with TalkBack I found some visible text that duplicates a button’s label. So this caused me to hear the text “do something” twice. Wasn’t sure if this was an issue but I checked with an expert, Roy Nickelson, and verified that this is a violation of the Level Access… Read more Andriod – Visible text that duplicates labels for controls

Alway maximize your web pages with zoom level set to 100% to ensure your screen reader can access all available content. Here is a great  blog post from Freedom Scientific on the topic.   Responsive Web Design: Why one site can behave differently on different PCs and browsers