accessibility | A repo to organize the guidelines and best practices | User Interface library

I'm reading through the WAI-ARIA specs and they state "The main role is a non-obtrusive alternative for 'skip to main content' links".

Now, I've never heard this, and the first few Google results I've seen are either out-of-date or point right back to the spec. Is there enough (any?) support among accessibility tools to consider phasing out "skip to content" links when a main role is present?

I try to Send data from Activity to AccessibilityService. There are solution i found 1 2 but it is not work. This is my code when i use 2:

in Activity this is my intent

I'm using ESLint with Angular and I don't like having extra code like (observable | async) === (false | null | undefined) instead of just (observable | async). How do I disable that rule?

I'm looking into utilizing accessibility APIs provided by macOS and Windows for an application.

The AX stuff for macOS works fine, I can get all the elements of a native Cocoa application.

The Windows APIs is also promising.

However, apps built with frameworks like Electron and such, which incorporate a "web view" are not accessible through the native APIs. They just appear as a black box. This is also the case using the Accessibility Inspector utility for macOS.

I'm not convinced this is a dead end though, because the macOS VoiceOver utility can dig into the web elements and inspect them. Are there separate APIs I need to use to get access to the web elements?

I am developing a barcode app and save the data to hive. What I need to know is there a way to export the saved hive database to a backup file and be able to retrieve it for instance if the app crashed or your phone is lost. This is for blind accessibility. Want to export the data to a file that I can save to my pc to store and if something happens I do not have to scan all the products again to build the database. If hive can not do this can someone point me in a direction of which flutter dart database can do this. Thank you

Ok the answer did not work for me. Here is a copy of my model file

For desktop browser sizes I have a navbar across the top of the page, when browser reduces to mobile size it becomes a hamburger menu. As the menu is hidden at mobile size, then for accessibility reasons I believe that, the elements within the menu need to have attributes of tabindex=-1 and aria-hidden=true. The website is being built using HTML/Jinja2, CSS, client side JS and Python/Flask.

As you can see from the CodePen below I am able to toggle the aria-hidden attribute once the menu has been opened.

[My demonstration repsonsive menu using CodePen] (https://codepen.io/janlikescodepen/pen/wvJmdBZ)

I see a lot of discussion on the internet about tags that look like buttons, and rules that all links must obey. However, I am confused about tags that are styled to look like links.

Are there any accessibility concerns with styling buttons to look like links? Would it make more sense to style these buttons as buttons? If they should look like buttons then what should be the priority? Does it make more sense just to hide the hidden "pages" with css, so that I can turn the buttons into tags and add an href?

I have a Xamarin app that was not meant to handle the talkback functionality of android, because for it to work well it had to be build in a specific way.

My app is a little order, and I simply can't make a do-over of the whole thing.

So, what is happening? My Xamarin app is made with non-native libs, that are not supported by the Talkback, so, when the user turns on the Talkback functionality the app effectively stops receiving the DPAD events since they are handled by the systems Accessibility Service.

That service, gets the events, and tries to handle them within my app, but, since my components are non-native, the system does not recognize them and the DPAD is wasted, hence, the illusion that the DPADs are not working.

So, what do you have to do if you just want to handle the DPADs (and nothing else) yourself with Talkback on?

The answer to this post will contain the code that describes the following behavior:

I am exploring tools I can use for automated Accessibility Testing and wanted to try axe-core with TestCafe. I am an advocate of TestCafe, I love that is a lightweight tool and doesn't have dependencies on WebDriver. The docs are great and the scripting is easy.

I have however found that @testcafe-community/axe and its predecessor axe-testcafe do not report all violations while axe-core with selenium and axe-webdriverjs do. For example, running with axe-webdriverjs, I have the following code and resulting output showing the violations of a localhost page I am checking -

Code: