Blog » Accessibility
What is Plain English? Plain English is English that’s friendly to read. Texts written in plain English are made to suit the reader. They should be:
Straight to the point Written in clear language Give information in an order that makes sense Many people are confused about why we use plain English. There’s a lot of information about it which is not true. Because of this, many people do not use it.
Currently, we are living in an era of co-existence between people and social media. More than ever, social media is playing an integral role in our daily lives. For many people, it has transformed into a primary form of communication. It’s one of the most popular forms of entertainment, and it’s also one of tech’s biggest money-makers. As a result of this, digital content creation has become a highly lucrative career path.
Since the birth of social media, blogging has remained one of the most popular and widely accessible forms of digital content. Each month, approximately 409 million people view more than 20 billion different blog pages. As of 2021, there are over 455 million websites on WordPress and that number is only going up.
Starting a blog can seem like a highly lucrative hobby and career path. Not only can blogs make good money, but they can be super cheap to start.
Globally, there are over one billion people with disabilities. That’s 15% of the population. Worldwide, there are also over one billion monthly Instagram users, 1.9 billion daily Facebook users, and 2.91 billion monthly YouTube users. These groups both have a massive population which is bound to cross over. So, it would make sense that all social media is made accessible, right? Unfortunately, this is not always the case.
A content creator’s aim is to make content that can be enjoyed by as large of an audience as possible.
Happy International Assistance Dog Week! It's that time of year to give our special helping hounds a big round of applause.
International Assistance Dog Week gives a massive thank you to all the dedicated service dogs that provide support for individuals with disabilities and other medical conditions as they navigate daily life. Here at PowerMapper, we would also like to give particular recognition to the trainers who dedicate so much time to training these dogs.
This post is a compilation of disability statistics from government agencies and researchers in the US, UK and Canada.
The statistics shown have most impact on website use, and help assess the impact of accessibility problems, in terms of
numbers of people affected, and likely commercial impact.
This posting summarizes some detailed research into the state of government accessibility standards around the world, as of March 2016. Usually these evolve fairly slowly, although the Jodhan vs. Attorney General of Canada case may change that (governments don't like being successfully sued by their citizens).
Search engines can't see and can't click, so there's a big overlap between making sites accessible and making sites perform well in search engines. Social media also uses several features that improve accessibility.
Summary The table element in HTML is not always treated as a table by assistive technology.
Historically HTML tables have been misused for layout. Before the introduction of CSS Grid in 2017 there was no reliable CSS method to layout HTML on a grid, so tables were often used instead (and some legacy browsers still don't support CSS Grid).
This means there are two types of table:
Data tables containing data where rows and columns have meaning (e.
Often scanning a large site finds a large number of issues. What's the best way to fix these?
Fix template issues Issues in page templates are often repeated on every page on a site, so fixing these has the maximum benefit. Template issues often affect site navigation, so even fixing minor issues has positive impact for users trying to navigate around the site.
It's not uncommon for template issues to account for 50% of the issues by volume, so fixing a single page template can resolve half of the issues found.
We've just released a new batch of screen reader test results. We started testing screen reader support for accessibility features in 2012. Since then we've run over 10,000 individual tests covering 54 browser and screen reader combinations.
New tests in this release cover:
NVDA 2019 with Chrome, Firefox and IE11 JAWS 2019 with Chrome, Firefox and IE11 VoiceOver with Safari on macOS 10.14 and iOS 12 This is the first release with tests results for Chrome.
A new batch of screen reader test results is now available.
New tests in this release cover:
NVDA 2018 with Firefox and IE11 JAWS 2018 with Firefox and IE11 VoiceOver with Safari on macOS 10.13 and iOS 11 A key finding is aria-label no longer works when reading links in JAWS 2018 with Firefox 60, but did work in previous versions of JAWS and Firefox as far back as 2012.
Update - January 2017 On January 5th, 2017 the US Access Board announced that the Office of Management and Budget (OMB) cleared the Section 508 Refresh, with the compliance deadline set for January 18, 2018.
Introduction Welcome to a series of articles on accessibility laws, standards, and statistics around the globe. These articles will help web professionals to understand accessibility legislation within a wider policy context. Every accessibility law has both strengths and weaknesses which can offer valuable lessons for other countries and systems.
Accessibility professionals can look forward to the passage of two European laws pertaining to web accessibility: the public sector accessibility directive and the European Accessibility Act. Both of these laws will bring much-needed clarity to the drive towards better accessibility in Europe. There are, however, a number of issues which will need to be resolved before the laws can be allowed to achieve their full potential.
This article explores both sides of a longstanding debate: should screen readers be detectable in analytics? It’s an issue that pits accessibility against privacy, with legal complications thrown in for fun. When these aspects are taken into consideration, screen reader detection emerges as a technique which carries serious technical, ethical and privacy risks.
Analytics Designers and developers live for analytics data. We can spend hours digging into fascinating insights on everything from shopping cart abandonment to social media conversions to browser use.
Summary This post describes how table cell headers for screen-readers are calculated.
TH with SCOPE=ROW or SCOPE=COL is unambiguous and widely supported TD with SCOPE is non-conforming in HTML 5, and is ignored as a header on some browsers (works in Apple WebKit, but ignored in Chromium WebKit). On tables with headers in the top row, or first column, TH without SCOPE usually works. TD HEADERS is problematic because it assumes a single list of headers for each cell, but accessibility APIs expose row and column headers as separate properties On any other table, TH without SCOPE produces wildly varying results.
This post follows on from the one on Disability Statistics,
and shows how the most common disabilities affect website use.
Well, it’s that time of year again. While I consider myself one of life’s formidably organised Christmas present buyers (I started in August) I seem to fall sadly short when it comes to finding the time to write and post my Christmas cards.
I know that to many, card writing seems an outmoded way of sending Christmas greetings, but for many of my ageing relatives, some of whom now live alone, a hand written card arriving in the mail is still much appreciated.
Today is World Stroke Day, which aims to raise awareness of the condition. Earlier this week I saw a conference keynote speech by Clayton Christensen, author of The Innovators Dilemma and a Professor at Harvard Business School.
He introduced himself by apologizing for hesitating while speaking because he'd suffered a stroke a few months earlier. In spite of this he was an engaging speaker - much better than the other professional conference speakers.
The Design for All Research Group at Middlesex University have produced a report called Declaring conformance on web accessibility asking the question: can website accessibility declarations be trusted?
Sadly the conclusion was no, for both self-declared and third-party certifications, confirming the findings of earlier studies. Using a sample of 100 European government and commercial sites claiming accessibility standards conformance, more than 95% were found to have accessibility issues. The study used our automated tool, SortSite, in conjunction with manual testing performed by the accessibility group at the Shaw Trust (see the report for details on methodology).
A few days ago I attended a presentation given by some UK Government departments - the main topic was providing equality of access to government contracts. There was the usual torrent of PowerPoint slides filled with facts, figures and addresses of websites which publish government contracts.
At the end of the presentations the question and answer session started:
Chief Official: "Does anyone have any questions?"
Lady in Audience: "Will any of the slides be available after the meeting?