@MrNibbles

While making a html page, I notice that NVDA reads "clickable" for every <p> or <span> tag. Is there a way to stop this?

I was running lynx to test some HTML I had to do, because having accessibility in mind.

Im doing a html page which has to be accessible.

I have the following bootstrap popover:

I have a form with 3 input fields and then a button that is shaped like a next symbol.

I want to detect whether a screen reader is running on a user's machine to avoid sound clashing with audio tag in html. If so, please provide details on how this could be done.

<input type="search" placeholder="search" />


• I have three 28" 4K screens plus some additional smaller ones on my main machine.

I have an Apache (2.4.10) web server running on a desktop with Debian (Jessie, 8).

I know you can change elements of web pages and some aspects of the outer "chrome" via custom themes, font family settings, etc.

If I use the Ctrl+ and Ctrl- key combinations I can lower my font size down to 8pt, even though if I edit my user preferences I can set this to whatever I like.

In our application we have a lot of lists falling under a single label.

With many of the commercial and corporate buildings now having more strict control around entries and exits, I was wondering in terms of accessibility how people with vision impairment are provided

I've stumbled on this very obvious idea while working on a website with a lot of interactive items that lead to separate pages.

I'm developing a serious game for collecting behavioral data and I need to convey to each player some status infor

I have a case where i have tabs and each tabs has a set of information.

I know that underlining non-link text is taboo because it confuses the user into thinking it's a link.

We have an application where users have to subscribe to health plans for 3,6,or 12 months.

I recently built a browser extension like Vimium