Showing posts from October, 2020

Day 30 Review the complexity of a website’s content with the Hemingway app.

  What is the Hemingway App? The Hemingway app is a distraction-free writing and editing tool designed to help you polish your writing. It focuses on identifying common errors that bring down the quality of your prose: confusing sentence construction, overuse of weak adverbs, excessive passive voice, and the like. You can use a free version of the app right on the website. There are two modes in the Hemingway app: writing and editing. Writing Mode The writing mode is designed to be unobtrusive, with a minimalist interface. Formatting buttons along the top allow you to make your text bold or italic, set your headings, add a blockquote or a list (either in bullet point or numbered), as well as create links. There are no page breaks, or detailed formatting options to create print layouts — this app is truly about writing, and writing only. Editing Mode Switch to editing mode, and you’ll see most of the Hemingway features come into play. In addition to a summary of your work’s readability

Day 29 Find 3 accessibility issues without using an evaluation tool.

There are many accessibility issues that  can’t be replicated by a machine or computer program, which makes manual accessibility testing essential for ensuring that your solutions are actually usable for visitors with specific disabilities.  Below are a few ways to test website accessibility manually: #1) We can use high contrast mode: Using high contrast mode we can highlight the content of the website. When we turn the high contrast mode, the content of the website gets highlighted automatically as it turns into white or yellow and the background turns black.After this, we can see if the content is properly visible or not. #2) By not accessing the Images : Temporarily for time being, you can turn off the access to image through your browser and see if the text-justify the content as some people may not have access to that or sometimes it takes too long to load the images. #3) Checking for captions : Check if a caption is available and make sure it is pretty much descriptive. Many ti

Day 27 Learn how to use your mobile device screen reader

  In Samsung smartphone Screen Reader uses a Voice Assistant that will describe what you touch, select and activate, giving you maximum control over your phone, even if you can't see it.This feature has previously been called TalkBack. To enable the screen reader  1 Go to setting 2 Tap on Accessibility 3 Tap On screen Reader     4 Tap the switch next to Voice Assistant 5 Voice Assistant uses your phone in specific ways and requires additional permissions. Tap Allow to give Voice Assistant the permissions it needs to function. The Screen Reader feature is now active. The controls of your device will have changed and all of your actions will be read aloud by the Voice Assistant. How to use screen reader Once the Screen Reader has been activated, the process of controlling your smartphone will change. When you interact with an item on the screen, a rectangular focus box will surround it. You can then use tap and swipe gestures to control the focus.  To hear what's directly unde

Day 26 of #30DaysOfTesting - Find an accessibility issue on a website and report it.

I found high colour contrast issue on the following website. I used WAVE & Colour  Contrast Analyzer for scanning. And results were as  follows.

Day 25 Explore W3C’s Before and After demonstration.

  The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards. W3C's mission is to lead the Web to its full potential. On their website ( ) you can find The Before and After Demonstration page which is a multi-page resource that shows an inaccessible website and a retrofitted version of this same website. Each web page includes inline annotations that can be activated to highlight some of the key accessibility barriers or repairs. Each web page is also accompanied by an evaluation report to inform the developers on the level of conformance to the Web Content Accessibility Guidelines (WCAG) . Here are two pictures of the home page they use for their example (there are several pages with before/after examples). I used WAVE tool to scan both before & after pictures for better understanding. As you can see in first picture we can see lots of error such as alternativ

Day 24 Web Accessibility Law in UK

Although the Disability Discrimination Act 1995 began to address website accessibility, it wasn’t until the Equality Act of 2010 (EQA) that legal protections for people with disabilities really expanded online. The Equity Act formally addressed that websites needed to comply with equal access and web accessibility standards. Section 20 of the EQA required service providers to take reasonable steps to provide an equal experience for people with disabilities both online and offline. Section 29 of the Act prohibits discrimination by failing to provide adequate accommodations for use. Additional regulations were also passed into law in 2018. The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 covered public sector websites and mobile apps. Who Does Web Accessibility Law Benefit? There are more than 13.9 million people classified as disabled in the U.K. representing 22% of the total population. In Ireland, 13% of the population has a disab

Day 22 & 23 Learn why semantic HTML is important & example of missing semantic

why semantic HTML is important. What is HTML HTML stands for Hyper Text Markup Language.It is the standard markup language for creating Web pages.HTML describes the structure of a Web page. It allows the user to create and structure sections, paragraphs, headings, links, and blockquotes for web pages and applications. HTML is not a programming language, meaning it doesn’t have the ability to create dynamic functionality. Instead, it makes it possible to organize and format documents, similarly to Microsoft Word. What is semantic  HTML Semantic HTML or semantic markup is HTML that introduces meaning to the web page rather than just presentation. For example, a <p> tag indicates that the enclosed text is a paragraph. This is both semantic and presentational because people know what paragraphs are, and browsers know how to display them. On the flip side of this equation, tags such as <b> and <i> are not semantic. They define only how the text should look (bold or italic

Day 21 Look for invisible keyboard focus when tabbing through a page.

Look for invisible keyboard focus when tabbing through a page. Keyboard accessibility is one of the most important aspects of the web accessibility. Some computer users are physically unable to use a mouse. Others prefer using a keyboard because it’s often more efficient. Computers in general, and web browsers specifically, can be operated with keyboard alone.  In web browsers, users can use the tab key to jump between focusable elements (i.e., links, form fields, and any other content that has been added to the tab order with the HTML tabindex attribute). When an item has keyboard "focus", it can be activated or manipulated with the keyboard. A sighted keyboard user must be provided with a visual indicator of the element that currently has keyboard focus. A basic focus indicator is provided automatically by the web browser and is typically shown as a border (called an outline) around the focused element. Invisible keyboard focus  can introduce difficulties for users who rely

Day 20 Write a simple accessibility checklist.

  Day 20  Write a simple accessibility checklist. The following checklist is based on the WCAG 2.0 Level A and AA standards.  Many of the items in the checklist apply to web pages and web-based applications as well as electronic documents in Microsoft Word, Adobe PDF, and other formats, and other products and services that are not specifically web-based. Perceivable Do images have alternative text ? Does video have captions and does audio have a transcript ? Does the web page or document include headings, lists, ARIA landmarks, and other semantic elements to communicate document structure? Is the tab order and read order logical and intuitive? Do form fields within web pages and documents have appropriately coded labels and prompts ? Have you avoided using visual characteristics to communicate information (e.g., “click the circle on the right” or “required fields are in red”)?  Does the interface have sufficient contrast between text color and background color? Does the content s