Artifacts Gallery Guilds Search Wiki Login Register

Welcome, Guest. Please login or register. - Thinking of joining?
a Summer day - @693.32 (what is this?)
Activity rating: Four Stars Posts & Arts: 77/1k.beats Random | Recent Posts | Guild Recents
News: :sleep: These are fast times on the World Wide Web~ Guild Events: HOMESTUCK ART-APALOOZA

+  MelonLand Forum
|-+  Life & The Web
| |-+  ☞ ∙ Life on the Web
| | |-+  IBM Equal Access Accessibility Checker - Opinions/experiences?


« previous next »
Pages: [1] Print Embed
Author Topic: IBM Equal Access Accessibility Checker - Opinions/experiences?  (Read 1263 times)
ThunderPerfectWitchcraft
Hero Member ⚓︎
*****
View Profile WWWArt


Here be dragons
⛺︎ My Room

Artifacts:
I got robbed by Dan Q on Melonland!Great Posts PacmanThanks for being rad!First 1000 Members!Joined 2023!
« on: a Winter night » Embed

There is a Firefox Add-On available to check for problems regarding the accessibility of a website, called the IBM Accessibility-Checker.

When I did a little project a while back I tried to use it to make the whole thing accessible (at least I hope so, I'm yet to get feedback about it :). My main page got some violations; reddit and github got many, this board here has over 80 violations. Are people around who know about accessibility for visually impaired people? Do you attempt to make your page accessible? What do you think about this tool for automatic checking - do you think it is sufficient to assume that a page that got no violations is usually usable for people who use a screen-reader (or similar devices), or do you think this is to imprecise? How serious are those "violations" - are they sure or likely to break the usability for impaired visitors, or are they usually rather nuisances? And what are your impressions about the development of the accessibility of websites in general?
Logged


Artifact Swap: Spell: Rain Storm (makes the player who holds this immune to fire magic)
varve
Jr. Member ⚓︎
**
View Profile WWW


⛺︎ My Room
RSS: RSS

Guild Memberships:
Artifacts:
Joined 2024!
« Reply #1 on: a Winter night » Embed

I think turning off CSS and image loading, and trying to use only a keyboard to navigate your site will show you a *lot* of the accessibility problems that a screen reader user might encounter. Because that's basically what they're doing, but with the text you see being read aloud to them.

(I'm told it also prefaces the element types with their name, so for example an image alt text starting with "image of" will be spoken as "image: image of", and buttons and links likewise are introduced. The screenreader-using folks I've talked to said for image descriptions, don't say what kind of image it is unless that's actually relevant, for example it's a painting or sketch, and if it's a functional or informative image focus the alt text on that instead of on what it looks like.)

I'm not surprised this site got loads of accessibility violations though.
Logged

Pages: [1] Print Embed 
« previous next »
 

Melonking.Net © Always and ever was! SMF 2.0.19 | SMF © 2021 | Privacy Notice | Send Feedback | Supporters ♥ Forum Guide | Rules | RSS | WAP | Mobile


MelonLand Badges and Other Melon Sites!

MelonLand Project! Visit the MelonLand Forum! Support the Forum
Visit Melonking.Net! Visit the Gif Gallery! Pixel Sea TamaNOTchi
MelonLand @000

Minecraft: Online
Join: craft.melonking.net