Day #25 Explore W3C's Before and After accessibility demonstration

I was exploring with Voice over screenreader for before and after the accessibility demonstration given by W3C. They explained well about text alternatives, keyboard accessibility, and other issues and how to fix them. 

Before and After accessibility demonstration site



Comments

Post a Comment

Popular posts from this blog

Testing Challenges

Image
 Day 30 # Review the complexity of a website's content with the Hemingway app  The Hemingway app is a popular free writing tool created by Adam and Ben Long. Hemingway Editor helps you to edit your writing so that your words are clear and powerful. The app checks your words and sentences which point out areas you can change to make your writing better. Hemingway Editor is easy to blogs, posts, business communication, fiction, essays, or academic papers. It is one of the quickest and easiest ways to find the passive voice and overused adverbs in your texts to make them easier to read.  There is a desktop version of the Hemingway Editor available for Mac and PC, which is quite cheap. But most users will prefer to use the free online writing editor. Hemingway Editor is simple to use.  First, copy your text.  Then go to https://www.hemingwayapp.com and delete the example text.  Paste your text into it and edit the highlighted things in your writing.  Everything is color-coded. Adverbs
Read more

WCAG 2.0 - WEB CONTENT ACCESSIBILITY GUIDELINES

Image
Day 5# 30 days of Accessibility testing Day#5 Read the 12 guidelines of Web Content Accessibility Guidelines (WCAG 2.0.) Write a short post on one of them    The Web Content Accessibility Guidelines (known as WCAG 2.1) are an internationally recognized set of recommendations for improving web accessibility. They explain how to make digital services, websites, and apps accessible to everyone, including users with impairments to their: • vision - like severely sight impaired (blind), sight impaired (partially sighted) or color blind people • hearing - like people who are deaf or hard of hearing • mobility - like those who find it difficult to use a mouse or keyboard • thinking and understanding - like people with dyslexia, autism, or learning difficulties WCAG 2.0 is based on 4 design principles: • Perceivable - Information and user interface components must be presentable to users in ways they can perceive. • This means that users must be able to perceive the information bei
Read more
 Day21 #  looking for invisible keyboard focus when tabbing through a page. I logged in twitter and started tabbing on the twitter page which is navigating on each tab on-page content. Tab-Usability Guidelines Here are 12 design guidelines for using tabs: 1. Use tabs to alternate between views within the same context, not to navigate to different areas. This is the single most important point because staying in place while alternating views is the reason we have tabs in the first place. 2. Logically chunk the content behind the tabs so users can easily predict what they'll find when they select a given tab. 3. Use tabs only when users don't need to see content from multiple tabs simultaneously. 4. Design tabs that are parallel in nature. If the tabs are significantly dissimilar, users will interpret them as site navigation. 5. Highlight the currently selected tab. Make sure that the highlighting is prominent enough so people can tell which tab is selected. 6. The un
Read more