Connect with us

WordPress

Why Your Website Must Be Compliant

Published

on

Why Your Website Must Be Compliant


In the U.S., apart from federal, state, and local government websites which must meet Section 508 regulations, there are no enforceable ADA legal standards to follow for website accessibility.

However, just because there is no straightforward set of legal requirements for website accessibility does not mean that your business will not be presented with a lawsuit. This has understandably raised alarm.

Most countries provide laws protecting the civil rights of disabled persons for homes, parks, businesses, and educational facilities. What is not universal is website accessibility.

The internet provides global access to information, stores, education, financial institutions, audio, and video, but often remains restricted or dependent on assistive devices for millions of people to gain unhindered access.

Fortunately, there are standards in place that unifies development and allows the world to use web-based solutions with universally accepted protocols. We know these standards as the World Wide Web Consortium, or W3C.

Accessibility guidelines are known as WCAG. As of 2018, we are at version 2.1. (Both WCAG and Section 508 guidelines were updated in 2018.)

Research Your Country

The weakness of website accessibility enforcement in the U.S.A. that encourages ADA lawsuits has not only driven up the number of lawsuits but has enabled some of them to reach beyond the States.

It is important to understand the laws and recommendations for web accessibility for your own country.

Both the U.S. and the U.K. refer to non-government related websites as “public” and “public sector” entities, allowing the legal system to hear cases brought by persons with disabilities who find themselves unable to use a public-facing business website.

In the U.S.A., this is referred to as the ADA Title III, Public Accommodations and Commercial Facilities. It has not been updated to include websites and online applications.

Europe updated its EU Web Accessibility Directive in September of 2018, making all public sector websites and applications in EU member states implement, enforce and maintain accessibility standards or risk fines and legal penalties.

Of their recommendations, accessibility statements are one that is gaining in popularity for everyone wanting to show initiative.

One popular guideline for businesses to use when deciding whether to develop accessible websites is that if there is a physical store that must legally meet accessibility requirements for public access, their website version should also do so.

Accessibility laws in the US remain up for debate.Legally enforcing website accessibility remains under discussion by the U.S. Government.

Navigating the History of Website Accessibility & the Law in the U.S.

Even though there are accessibility standards and guidelines to follow, companies are not legally bound to apply them in the United States.

There is no official set of website accessibility standards or criteria set forth by the Department of Justice for businesses to legally comply with, other than Section 508 under Title II.

So why are there so many lawsuits?

On July 26, 1990, the late President George H.W. Bush signed into law the Americans with Disabilities Act (ADA), which is a civil rights law prohibiting discrimination on the basis of disability.

Its purpose is to protect the rights of individuals with disabilities for employment, access to state and local government services, places of public accommodation, transportation, and more.

On July 26, 1991, the DOJ issued its final rules for following Title II and Title III but neither addressed website accessibility.

Title II of the ADA applies to state and local government entities. It protects individuals with disabilities from discrimination on the basis of disability in services, programs, and activities provided by state and local government entities. What we refer to as Section 508 web accessibility falls under Title II.

Title III prohibits discrimination on the basis of disability in the activities of places of public accommodations. These are businesses that are generally open to the public and there are 12 categories, including schools, recreation, offices, and medical buildings.

Your ecommerce website and public mobile applications fall under Title III.

Section 508 & Title II

In June 2003, in recognition of how the Internet was transforming interactions between the public and governmental entities, the DOJ published Accessibility of State and Local Government Websites to People with Disabilities, to provide state and local governments guidance on how to make their websites accessible and ensure that persons with disabilities have equal access to the services, programs, and activities that are provided through those websites.

Title III was not included with this update.

The gap between government and public website accessibility began to confuse companies that conduct online business with the government and schools with websites, such as universities that accept federal financial aid.

Website Accessibility Roller Coaster

There have been attempts to add website accessibility enforcement support over the years.

Each has been met with failure.

ANPRM, NPRM & SANPRM

On September 30, 2004, the DOJ began the process of updating the 1991 regulations based on the relevant parts of the ADA and Architectural Barriers Act Accessibility Guidelines by publishing an Advance Notice of Proposed Rulemaking (ANPRM) and inviting public comment.

On June 17, 2008, the DOJ issued a Notice of Proposed Rulemaking to adopt the revised 2004 ADA/ABA Guidelines and revise Title II and Title III regulations. The 2008 NPRM addressed the issues raised in the public’s comments to the 2004 ANPRM and sought additional comments.

Neither the 2004 ANPRM or 2008 NPRM included a proposal for web accessibility provisions despite public comments urging the DOJ to issue web accessibility regulations under the ADA.

The ADA Amendments Act of 2008 went into effect on January 1, 2009.

Among other things its purpose was to make updates to the existing law and carry out the ADA’s objectives of providing:

  • “a clear and comprehensive national mandate for the elimination of discrimination”
  • “clear, strong, consistent, enforceable standards addressing discrimination by reinstating a broad scope of protection to be available under the ADA”

On July 26, 2010, the DOJ published an ANPRM titled Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities and Public Accommodations. This was the first attempt to include website accessibility enforcement.

On September 15, 2010 Titles II and II were revised again and called the 2010 ADA Standards for Accessible Design. They did not include web accessibility.

Hopes were raised when in the fall of 2015, the DOJ released a Statement of Regulatory that included three paragraphs on website accessibility.

This document addressed the realization that it became impractical to separate Title II (Government websites) and Title III (public websites) because they are often blended together. The document states:

“Public entities are increasingly providing their constituents access to government services and programs through their web sites. Information available on the Internet has become a gateway to education, and participation in many other public programs and activities. Through Government web sites, the public can obtain information or correspond with local officials without having to wait in line or be placed on hold. They can also pay fines, apply for benefits, renew State-issued identification, register to vote, file taxes, request copies of vital records, and complete numerous other everyday tasks.”

“Consequently, the Department is planning to amend its regulation implementing title II of the ADA to require public entities that provide services, programs or activities to the public through Internet web sites to make their sites accessible to and usable by individuals with disabilities.”

It went on to state that they “will be publishing separate NPRMs addressing web site accessibility pursuant to titles II and III of the ADA. The Department expects to publish the title II NPRM early in fiscal year 2016.”

That never happened.

In April 29, 2016, the DOJ issued a new SANPR called Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities”.

It is one of four ADA rulemaking documents that were removed and are now archived.

This particular document provides real insight into what’s complicating matters and why the government is unable to come up with any formal legislation on website accessibility.

It’s worth reading if you want to understand the history and read the public comments.

Next, the House of Representatives introduced H.R.620, ADA Education and Reform Act of 2017 which stalled in the Senate. There were many issues with it, from costs to the lack of what accessibility standards would be enforced and most importantly, the responsibility for resolution fell to the disabled plaintiff, not the business.

On June 20, 2018, 103 members of the U.S. House of Representatives drafted a letter to then Attorney General of the Justice Department, Jeff Sessions, regarding the flood of lawsuits and the ease of litigation when there are no legal standards to follow.

On September 25, 2018, the DOJ responded in a letter to Congressman Ted Budd. It references the withdrawal of the four rulemaking attempts to address website accessibility and the ADA and why.

The DOJ is “evaluating whether promulgating specific web accessibility standards through regulations is necessary and appropriate to ensure compliance with the ADA.” It references two Executive Orders covering the reduction of regulations and controlling costs.

In addition, this section caught the attention of law firms:

Absent the adoption of specific technical requirements for websites through rulemaking, public accommodations have flexibility in how to comply with the ADA’s general requirements of nondiscrimination and effective communication. Accordingly, noncompliance with a voluntary technical standard for website accessibility does not necessarily indicate noncompliance with the ADA.”

So basically in the U.S., it is your choice.

Now What?

Preventing anyone from conducting tasks online is risky. Since there is little in the way of federal website accessibility law, some states are moving forward with their own decisions.

Last year the first case to go to trial occurred in Florida. It resulted in Winn-Dixie (Gil v. Winn-Dixie) being required to pay $250,000 to bring its website up to WCAG standards.

That case is now being used in oral arguments in an appeal for a case against Dominos (Robles v. Domino’s Pizza).

In 2017, 7,663 ADA Title III lawsuits were filed in Federal Court, 1,062 more than 2016. Compare that with 2013, when there were only 2,722 cases.

Of those filed in 2017, a small number were for websites. Although one law firm projected a 30 percent increase in website accessibility cases for 2018, Usable.net tracked 2,285 website lawsuits — up 181 percent over 2017.

The use of assistive devices enables disabled persons to gain access to digital properties which may or may not be ready for them to use once they arrive.

Can they book a hotel room from their mobile device using voice commands?

Where does website accessibility fit with search engines and answer engines?

Ecommerce sites have long been targets for lawsuits.

The store brand, Target, lost their case and it cost them millions.

Nearly every well-known store brand, including Amazon, has faced an accessibility lawsuit.

Other verticals seeing legal challenges are hotels, travel, healthcare, financial institutions, and educational facilities.

Online courses, mobile applications, and progressive applications are next.

Another area presenting barriers to accessibility is how websites are made.

Low cost, pre-fab, template-driven websites are less likely to be accessible and their owners not educated on what they need to know.

WordPress was in the news for allowing Gutenberg to be released to the public before meeting accessibility compliance for developers using assistive devices.

WordPress core prides itself on meeting WCAG standards, but once you throw a theme and plugins into it, all bets are off.

Accessibility statements provide a small glint of hope for companies hoping to signal that they care about accessibility.

While not legally binding, an accessibility statement is like a privacy policy. There are proper ways to write them and not every accessibility expert recommends using them at all.

Design for Inclusion

Design for inclusion is hot for 2019.

From a branding and reputation perspective, search engines, conversions, revenue, and customer service brownie points, designing for accessibility is strongly recommended.

Companies with digital properties that are looking for investors would be wise to consider meeting accessibility standards, especially if looking to be attractive to potential buyers. For any online business, an accessible website may be your competitive advantage.

Unfortunately, left as a choice, companies routinely leave accessibility out of their development cycles because they:

  • Often do not have trained employees.
  • Don’t understand their target market.
  • Feel it is too expensive or it drags out the timeline
  • Are simply unaware of the various needs of their users.

This may no longer be an option.

How Do I Make an Accessible Website?

You may discover conflicting information on not only if your website should meet accessibility standards, but how to go about doing that.

Just as with the confusion over ADA website accessibility, there are ways to go about development and testing, as well as companies taking advantage of lawsuit fears hoping to lure in unsuspecting website owners.

There are easy basics to start off with for WCAG2.1 AA and free accessibility tools to discover the low-hanging fruit such as poor color contrasts and missing alt text.

In my next article for Search Engine Journal, I’ll address accessibility testing and why it matters. Because you likely figured out by now that it is safer to be prepared.

For Your Reference

More Resources:


Image Credits

Featured Image: Unsplash
In-Post Image: Unsplash

Subscribe to SEJ

Get our daily newsletter from SEJ’s Founder Loren Baker about the latest news in the industry!

Ebook





Source link

Continue Reading
Click to comment

You must be logged in to post a comment Login

Leave a Reply

WordPress

Leaning into SEO as Google shifts from search engine to portal

Published

on

Leaning into SEO as Google shifts from search engine to portal


Google’s SERP is almost unrecognizable compared to what it looked like just a few years ago. The changes aren’t just on the surface, either: Google is becoming less search engine, more portal, said Jessica Bowman, CEO of SEO In-house  and Search Engine Land editor at large, during her keynote at SMX Advanced this month.

This evolution is fundamentally altering the customer journey from search, with Google owning the process by enabling users to bypass clicks to websites to get information, take action and even transact. This will have repercussions for just about every company. Bowman offered several plans of action for SEOs preparing for these changes and said investments in SEO will be more important than ever.

Build and train your SEO army

“When I evaluate an organization, I find that every role has activities they do that affect SEO, and SEO needs to be integrated into those activities,” Bowman told Search Engine Land, “The SEO team has to figure out what those are and then train people to do that.”

Larger companies should incorporate SEO into their daily vernacular, said Bowman. This way, you can conscript dozens, if not hundreds, of staff members into your “SEO army,” get them advocating for it, quoting best practices, involving the dedicated SEO team and flagging missing requirements on a day-to-day basis.

Although non-SEOs aren’t expected to be authorities on the topic, their 20% of effort stands to make 80% of the impact on your brand’s overall optimization, Bowman said. It will be up to your main SEO team as well as upper management to empower them.

Expand writing competencies

Product information, news stories, how-to guides and various other types of content may receive higher visibility on SERPs if they appear as a knowledge panel, within a carousel or as a featured snippet. Your writers, be they bloggers, copywriters, social media managers or anything in between, need to be creating content that is comprehensive and authoritative enough to compete for organic visibility, said Bowman.

Writers across the company need to master concepts such as SEO-friendly JavaScript, schema, writing for the long tail, rich snippets and the “People also ask” section in the search results. As with any process, regularly reviewing copy and providing feedback can help assure quality and enable you to get the most from your efforts.

Master Schema and JavaScript for SEO

Understanding and correctly implementing schema on your site can help crawlers make sense of your content and, consequently, increase the odds that it gets displayed as a featured snippet. Featured snippets and other rich results, of course, illustrate the double-edged sword nature of Google’s portal-like interface: They increase your content’s visibility and yet users may not click through to your site because the information they need has already been presented to them.

Event, FAQ, speakable content and much more — Google now supports dozens of markups for various content types, making schema a valuable tool for modern SEO. If you’re using WordPress’ CMS, Yoast has revamped its schema implementation to streamline structured data entry, but it’s still important for your development team to be able to verify the quality of your code.

With Googlebot’s latest update, it can now see more of your content than ever. However, limitations still exist and brands should be cognizant of JavaScript issues that may hinder indexing. Before coding JavaScript, your teams need to be discussing what content search engines will and won’t be able to see. It’s also worth keeping in mind that other search engines may not be as equipped to render your content.

“Particularly for large, global companies, they need to think about these smaller search engines that are less sophisticated than Google but still drive a decent amount of traffic in international markets,” Bowman emphasized.

Monitor and study mobile SERPs

“The problem is, a lot of us work on our computers, and so we’re checking things out on the desktop interface,” Bowman pointed out. Beginning on July 1, all new sites will be indexed using Google’s mobile-first indexing, with older sites getting monitored and evaluated for mobile-first indexing readiness. Since the majority of searches now happen on mobile, brands need to closely examine the mobile SERP and account for updates and changes in order to create content that’s optimized for the devices their audiences are using.

“I think the reason that we, as an industry, have not been talking about this is because of that — we’re not really studying the search results on a mobile interface to truly see they’re [Google] taking it over, and as mobile takes over, they’re going to gobble up some of our traffic. I think once they’ve got it [the mobile SERP] mastered and they know it’s a strong user experience, it’s only a matter of time before they do that to desktop as well.”

Take advantage of big data

“Hiring a data scientist is better than hiring an SEO to study the data,” Bowman stated simply. Data scientists are better equipped to identify commonalities and trends that you can use to improve your optimization efforts, inform your content strategy and enhance user experience (UX).

During her keynote, Bowman also recommended that brands make use of the Google Chrome User Experience Report to compare site speed to the competition as well as reference UX metrics from popular destinations across the web. You can then be more proactive.

Google’s search results interface has changed dramatically, but brands and agencies that can shake the inertia, rally their staffs and reorient their processes will be the first to spot new opportunities and novel ways to reach their audiences.


About The Author

George Nguyen is an Associate Editor at Third Door Media. His background is in content marketing, journalism, and storytelling.

Continue Reading

WordPress

Yoast, Google devs propose XML Sitemaps for WordPress Core

Published

on

Yoast, Google devs propose XML Sitemaps for WordPress Core


The inclusion of XML Sitemaps as a WordPress Core feature has been proposed by a group of Yoast and Google team members as well as other contributors. In addition to a basic XML Sitemap, the proposal also introduces an XML Sitemaps API that would extend functionality for developers and webmasters.

The proposed XML Sitemaps structure. Image sourced from Make WordPress Core.

What it’ll include. The proposal states that XML Sitemaps will be enabled by default, allowing for indexing of the following content types:

  • Homepage
.
  • Posts page
.
  • Core post types (Pages and Posts)
.
  • Custom post types
.
  • Core taxonomies (Tags and Categories)
.
  • Custom taxonomies
.
  • Users (Authors)
.

It’s worth keeping in mind that your WordPress site’s automatically generated robots.txt file will also reference your sitemap index.

What it won’t include. Although the proposed feature will include the majority of WordPress content types and meet search engine minimum requirements, the initial integration will not cover image, video or news sitemaps, XML Sitemaps caching mechanisms or user-facing changes such as UI controls that exclude individual posts or pages from the sitemap.

The XML Sitemaps API. Here’s how the API will let you manipulate your XML Sitemaps:

  • Provide a custom XML Stylesheet
.
  • Add extra sitemaps and sitemap entries
.
  • Add extra attributes to sitemap entries
.
  • Exclude a specific post, post type, taxonomy or term from the sitemap
.
  • Exclude a specific author from the sitemap
.
  • Exclude specific authors with a specific role from the sitemap
.

Why we should care. Sitemaps facilitate indexing by providing web crawlers with your site’s URLs. If implemented, this might mean one less third-party plugin that brands and webmasters have to rely on for their SEO efforts. As a WordPress Core feature, we can expect wider compatibility and support than we might get from third-party solutions.

Poorly optimized plugins can also slow down your site, which can have a negative impact on your organic traffic. This default option from WordPress may not replace plugins like Yoast SEO because they often include other features in addition to XML Sitemaps, but its availability has the potential to provide us with more flexibility over which plugins we install.


About The Author

George Nguyen is an Associate Editor at Third Door Media. His background is in content marketing, journalism, and storytelling.

Continue Reading

WordPress

Yoast SEO 11.4 adds FAQ structured data, UX improvements

Published

on

Yoast SEO 11.4 adds FAQ structured data, UX improvements


Yoast SEO’s latest update enhances its FAQ blocks by automatically generating structured data to accompany questions and answers. The update also introduces some UX improvements and addresses issues with AMP pages when viewed in Reader mode.

How to use it. Yoast’s FAQ structured data implementation is only compatible with the WordPress block editor (also known as Gutenberg; available on versions 5.0 and newer). Webmasters can get started by selecting the FAQ block, adding a question, inputting the answer and an image (if applicable) and repeating the process for all frequently asked questions.

The Yoast FAQ block.

The corresponding FAQpage structured data will be generated in the background and added to Yoast’s structured data graph, which may help search engines identify your FAQ page and figure out how it fits into the overall scheme of your site.

A new action and filter were also introduced to make this integration more flexible. The wpseo_pre-schema_block-type_<block-type> lets you adjust the graph output based the blocks on the page and the wpseo_schema_block_<block-type> filter enables you to filter graph output on a per-block basis.

Other improvements. Yoast has also linked the SEO and readability scores in the Classic Editor and relocated the Focus keyphrase field to the top of meta box and sidebar to make it easier to find. And, they’ve resolved issues with AMP pages when viewed in Reader mode.

Why we should care. At this year’s I/O conference, Google announced support for FAQ markup, which may mean that searchers will be presented with FAQs as rich results more frequently. Being able to easily and efficiently equip our FAQ sections with structured data can yield better odds of earning prominent placement on SERPs.

For more on Yoast’s structured data implementation, check out our coverage on their 11.0 (general schema implementation), 11.1 (image and video), 11.2 (custom schema) and 11.3 (image and avatar) updates.


About The Author

George Nguyen is an Associate Editor at Third Door Media. His background is in content marketing, journalism, and storytelling.

Continue Reading

Trending

Copyright © 2019 Plolu.