New answers tagged

0

Text is important, because for some users who would be using your project would get confused with only icons, this would lead to a Bad User Experience. But then again if your Project already has too many data to be shown(on each pages) then adding extra texts just for icons may cluster your screen with too many things, so in my opinion, If the contents on ...


3

Normally my advice would be to always pair an icon with text on the screen, making both clickable. In this way you can use an aria-hidden attribute to hide the icon for screen readers, which just leaves the text link for audio screen readers. However, if it is not possible to do this, then you have to consider that someone cannot see the screen because they ...


-1

Text is an important part of UI development for AA. So the best choice would be including text.


0

You should use a long description or preferrably MathML. Here's more info. http://accessibility.psu.edu/math/


0

Use monospaced fonts to your advantage? Total account Days in the current month Fee = balance x Interest rate % x ------------------------------ as of 12 Jan Full length of service in days Or if you don't want to break up the "terms" over multiple lines, put ...


0

I find a dark on light works well, but not a white background. I find a muted light color or grey works better than pure white when using backlit LCD or LED monitors. I find black on #DBD2BF, #C5D3D6, #D6C7CB, #BDC7BD, or #C2C2C2 work as good examples.


4

Stop using "user-scalable=no". Period. In the last 6 years, I cannot count the times that I've had to put away the iPhone and go to a desktop computer to examine something on a website because it simply wasn't visible and there was no way to increase its size because of this particular meta-tag. This is far and away the most useless tag. I wish it had ...


7

I cannot answer #2, but I can take a stab at #1 with some explanation. Background The Web Content Accessibility Guidelines (WCAG) 2.0 (the basis for Section 508 in the US, some international regulations, and the ADA guidelines that the DoJ has used in recent lawsuits) have some guidelines on this. Success Criterion (SC) 1.4.1: Use of Color: Color is ...


2

There are many ways to address this, essentially the aim is to differentiate links from other text on a site. While an underline is the default way that browsers make this apparent, you could use a high contrast color difference, a 'highlight' effect, a custom bottom border, or a link icon. I think the best approach to this is to think of your aim and why ...


0

I am deaf myself and would always appreciate SMS. It would be nice if you could create a form like this: Phone number: [xxx-xxx-xxxx] [ ] text message only That way, you know the phone is only for text (regardless of their ability) and if it's not checked, you know they can use voice as well.


0

You might need ARIA attributes to make your panel behave like a drop-down field (which is essentially what you are simulating with your filter panel). Alternatively just use a standard html drop-down field instead of a panel (i.e. select & option elements). Why make this more complicated for you or your user? Using a drop-down would mean you get all the ...


4

I have no idea what your tool is unhappy about but there are no accessibility issues with drop-down fields containing 31 items, even when you use the value attribute. I suspect you are misunderstanding one of the WCAG2.0 requirements, e.g. Technique H85 for Success Criterion 1.3.1 (Info and Relationships) https://www.w3.org/TR/WCAG20-TECHS/H85.html As you ...


4

Tab is for switching between elements, not selecting different items within the same element. I think this is why the problem arises. Your element is similar to a drop-down list. Typically tab would allow you to select that list, but not iterate through the items in the list. Using the same key for both selecting and iterating through a control results ...


0

Imho, I think you shall only render items in the DOME when these items shall be used/when the user asks for them. One exception might be skip-links. From the accessible point of view, a screen reader won't se these items until they are rendered. From the performance point of view, if you render the items when they are required the page will load faster ...


1

Your sentence could be improved by replacing the "input device" bit. This is not user's language so try to use more familiar and less formal words, like "try to gesture with your finger or move your mouse to draw". Of course this is not the optimal sentence and it can be improved. What else you can do is detect users device, whether it is mobile or desktop ...



Top 50 recent answers are included