Author: minidev

The Great Need for Federal Website Accessibility

As a melting pot of sorts, the United States prides itself on the spirit of inclusivity. However, recent data released by the Department of Justice (DOJ) demonstrates a glaring gap in this principle — one in 10 tested federal websites are not fully accessible to people living with disabilities, leaving them barred from crucial government services.

The department released the data in the wake of increasing pressure from Senator Bob Casey, who had led bipartisan efforts and investigations into the issue. About three in five internal websites at major federal departments were equally found to be inaccessible, a failing grade by all standards. These results derived from tests conducted in collaboration with the General Services Administration.

The implications of these lapses are immense for disabled veterans, older adults, and people with disabilities at large. They pose barriers to these demographics’ access to information about COVID-19, filing claims, accessing health care, among other essentials.

The Importance of Accessibility

The Rehabilitation Act’s Section 508 demands that all of the US government’s IT resources be accessible to people with disabilities. A mandate that, it appears, not all agencies are keen to adhere to.

Few things could illustrate the value of technology in today’s world better than the ongoing pandemic, making this disregard for accessibility an even bigger slap in the face for veterans, older Americans, and the disabled community. Significant technological strides have occurred over the last decade, and it’s disheartening that many agencies haven’t made efforts to incorporate those advances into their work.

Unfortunately, some departments and agencies, including the Department of Justice (DOJ) itself, the Department of Defense, the Department of Agriculture, and the Environmental Protection Agency, didn’t even have adequate staff trained to implement Section 508 compliance policies or committed resources to the same. That few federal employees directly support these programs is also cause for significant concern.

Moving Forward

While these revelations are upsetting, the good news is that actions can be made to rectify the situation. Senator Casey, for instance, has consistently advocated for improvements. The Senator’s record of service on this issue reflects this tenacity.

Clearly, better integration of Section 508 compliance into federal agencies’ services is necessary. Alongside this, efforts need to be made to commit the needed resources to these duties and ensure all staff members undergo proper training. Given the importance of digital platforms for disseminating critical information, it’s no longer optional for the government’s resources to be readily available for people with disabilities.

---

Tags: #FederalWebsites, #Accessibility, #Section508, #DisabledAccess, #DigitalDivide
Reference Link

Sometimes while working with Amazon Redshift Spectrum, users might try to access data stored in Amazon Simple Storage Service (Amazon S3) buckets within the same account and encounter some problems. In addition, AWS Glue might be used as the data catalog. This post will provide answers and solutions when you experience permission errors in this situation.

Understanding Permission Errors

In scenarios where the AWS Identity and Access Management (IAM) role that’s attached to the Redshift cluster does not have adequate permissions on the AWS Glue and S3 services, several errors may occur:

1. While creating an external schema, users may encounter this error:

   SQL Error [XX000]: ERROR:

2. Trying to query a Redshift Spectrum table can result in this error:

   SQL Error [XX000]: ERROR: Spectrum Scan Error

3. If the S3 bucket uses a Key Management Services (AWS KMS) encryption key and you try to query a Redshift Spectrum table, this error may occur:

   SQL Error [XX000]: ERROR: Spectrum Scan Error

Resolving These Errors

The solution to these errors is to attach an IAM policy with the required permissions to the IAM role used by Amazon Redshift. If the S3 bucket is encrypted using a KMS key, users must also attach permissions to use the key.

Step 1: Create an IAM policy

The first step towards resolving these errors is to create an IAM policy and then attach it to the IAM role that is attached to the Redshift cluster. This policy will allow read access to the S3 bucket where the data is stored. Here is an example:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:GetObject",
        "s3:ListBucket"
      ],
      "Resource": [
        "arn:aws:s3:::bucket_name/*",
        "arn:aws:s3:::bucket_name"
      ]
    }
  ]
}

Note: Replace “bucket_name” with the name of your bucket.

Step 2: Add Permissions for KMS Encrypted S3

If the S3 bucket that Redshift Spectrum is using is encrypted using an AWS KMS encryption key, then create and attach the following IAM policy. Attach the policy to the IAM role that’s attached to the Redshift cluster. This policy provides access so that Redshift Spectrum can decrypt the encrypted data in Amazon S3. Here’s an example of the minimum permissions to allow decryption:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "kms:Decrypt"
      ],
      "Resource": [
        "arn:aws:kms:<region>:<AWS account ID>:key/<KMS key ID>"
      ]
    }
  ]
}

Note: Replace “”, “”, “” with your respective details.

In conclusion, ensuring that the IAM role associated with your Redshift cluster has the right permissions with the AWS Glue, S3, and possibly KMS services, saves you a lot of trouble and prevents unexpected permission errors.

Tags: #AWSRedshift, #AmazonS3, #AWSGlue, #IAM

[Reference Link](!https://repost.aws/knowledge-center/redshift-resolve-access-denied-errors)

As a data scientist, setting up a static site on your S3 instance can be an exciting achievement. But what if you begin to encounter an Error 403 AccessDenied when trying to access your site through CloudFront? This error can be quite frustrating and understanding why it’s occurring and how to resolve it can save you a lot of time and effort. This post aims to walk you through the necessary steps to troubleshoot and fix this common issue.

Understanding the Error 403 AccessDenied

Before getting started with the troubleshooting process, it’s important to understand what this error means. An Error 403 AccessDenied typically indicates that the request made was valid, but the server is refusing to respond to it because it does not have the necessary permissions to access the requested resource.

Troubleshooting Steps

Step 1: Check Your S3 Bucket Policy

Your S3 bucket policy is what defines who can access your bucket and what actions they can perform. The first step in resolving the Error 403 is to ensure that your bucket policy allows CloudFront to access your S3 bucket. Here is an example of such a policy:

{
  "Version": "2012-10-17",
  "Id": "PolicyForCloudFrontPrivateContent",
  "Statement": [
    {
      "Sid": "1",
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::cloudfront:user/CloudFront Origin Access Identity EAFQXXXXXXXX"
      },
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::your-bucket-name/*"
    }
  ]
}

Step 2: Enable Public Access

CloudFront serves your content to the public, hence, it’s essential that your S3 bucket allows public access. To do this, navigate to the ‘Permissions’ tab in your S3 bucket settings and turn off the ‘Block all public access’ option.

Step 3: Double Check Your CloudFront Origin Settings

Your CloudFront distribution’s origin settings are another crucial part of this puzzle. You need to ensure that the origin domain name matches your S3 bucket’s name and that the ‘Origin Access Identity’ is the same as the one you specified in your S3 bucket policy.

Step 4: Invalidate Your CloudFront Cache

After making changes to your S3 bucket or CloudFront settings, CloudFront may still be storing and serving the old version of your site. To make sure CloudFront fetches the latest version of your site from your S3 bucket, you’ll need to invalidate your CloudFront cache. You can do this by creating an invalidation request with the path set to ‘/*’.

Conclusion

By carefully following the above-mentioned steps, you should be able to solve the Error 403 AccessDenied when accessing your S3 static site via CloudFront. Understanding how to manage and troubleshoot your AWS services is key to maintaining your applications and becoming a more proficient data scientist.

Stay tuned for more technical guides and tips!

Tags: #AWS #Troubleshooting #CloudFront #S3Bucket

[Reference Link](!https://saturncloud.io/blog/troubleshooting-error-403-accessdenied-in-cloudfront-for-your-s3-static-site/)

Powered by ChatGPT, Flowy is an accessible design solution by Equally.ai that is set to influence the web development industry profoundly. With the integration of artificial intelligence (AI) capabilities, Flowy is leveraging advanced tech to tackle web accessibility challenges, making the internet a more accessible place.

About Flowy

Flowy is an automated process for improving accessibility compliance, making the development and maintenance of accessible websites efficient, scalable, and cost-effective. This automation encourages developers to build innovative products without stressing over the intricacies of accessibility.

One of Flowy’s standout features is its recommendation engine, providing developers with suggestions for remedying accessibility concerns. This system empowers developers to maintain the quality of their products throughout development with minimal extra work. The product generation sparks optimism and anticipation for Dani Zeevi, Equally.ai’s board chairman, who sees endless possibilities with this groundbreaking technology.

What Can Flowy Do For You?

From large global brands to small businesses, website owners can take advantage of Flowy’s all-in-one platform, equipped with features like recommendations, guidelines, explanations, and solutions for implementing essential modifications. The application simplifies the entire accessibility testing process. Developers can sort accessibility problems, address them, and access constant compliance reports.

The solution presents multiple benefits, including saving developers’ time, energy, and resources. In addition, it significantly mitigates the legal risks associated with not providing web accessibility.

Cloud Access and Chrome Extension

Priced at $27/month with a free trial, Flowy offers both a cloud-based platform and a Chrome web browser extension. The cloud-supported dashboard serves as a centralized point for managing all accessibility needs in a visually engaging interface.

The Chrome extension acts as a real-time accessibility auditing tool, offering immediate insights and actions to enhance website accessibility.

Integration of ChatGPT

Flowy is an innovative application of the ChatGPT technology by OpenAI. This technology delivers detailed responses and answers in various knowledge domains, making it extremely useful in the realms of language and computer coding. Flowy seems to be the first developer tool leveraging ChatGPT, creating a bridge between complex technical evaluations and the realization of practical accessibility solutions.

The Impact on Accessibility

Flowy represents a significant leap forward in the development space, aiding website owners and developers in navigating the complexities of web accessibility. It offers an essential solution to developers who wish to create accessible sites without needing to become accessibility experts.

A Journey of Development

Equally.ai had been working on Flowy for over a year when they partnered with Microsoft’s developer program. This partnership offered early access to OpenAI and led to the full integration of ChatGPT into Flowy.

Overcoming the Challenges

As is the case with any AI development, accuracy was a challenge. Equally.ai had to invest in a specialized team to ensure the solution’s efficiency and accuracy. They have devised rigorous system monitoring to keep the AI’s performance in check and continuously optimize Flowy for better accuracy and reliability.

How Does Flowy Work?

Flowy’s first step is scanning website code for accessibility errors, which it then categorizes based on their severity. It provides the best suggestions for remedying these issues, and the platform also checks for new accessibility problems regularly, alerting the user when any are detected.

Concluding Remarks

Through its AI driven features and user-friendly design, Flowy is streamlining the process of creating and maintaining accessible websites, ensuring that the internet becomes a more accessible place for all.

---

#WebAccessibility #AI #OpenAI #Flowy #WebDevelopment

[Reference Link](!https://www.technewsworld.com/story/ai-smart-flowy-automates-accessibility-fixes-to-make-websites-usable-for-all-177918.html)

With the rise in the use of assistive technologies (AT) in enhancing and facilitating web accessibility, it’s crucial for developers to understand how ARIA (Accessible Rich Internet Applications) can work with these technologies. However, there tends to be some level of inconsistency in ARIA support across different user screen readers and web browsers. It is for this reason that the importance of ARIA’s first rule cannot be overstated: wherever possible, semantic HTML should be relied upon. However, ARIA remains an essential tool for web accessibility, especially where content cannot be semantically defined using native HTML or for web sites with complex or dynamic content.

ARIA Support Tables: A New Step

In a recent move towards comprehensively addressing the inconsistency issues, the ARIA and Assistive Technologies Community Group (ARIA-AT) announced the publication of its first Assistive Technology Support tables in April 2023. These tables are available through the ARIA Authoring Practices Guide (APG) and are designed to indicate how ARIA is supported by various combinations of screen readers and web browsers.

As a starting point, these support tables only detail pattern implementations for three screen readers and a limited number of patterns but promise more updates in the future according to the World Wide Web Consortium’s (W3C) official announcement.

Making Sense of the AT Support Tables

The introduction of AT support tables is a significant step in overcoming the challenges that developers face when they attempt to code for assistive technology users. These tables help to predict screen reader behaviors, providing important insights for developers who are not regular screen reader users.

The ARIA-AT group recognizes the struggle developers face in creating experiences that are accessible to users of all assistive technologies. Coding for one AT may result in a less optimal experience for another AT. The AT support tables can help to prevent this.

Current and Future Support Tables

Currently, five ARIA authoring pages feature these AT support tables:

• Button Examples
• Link Examples
• Radio Group Example
• Using aria-activedecendant
• Alert Example

The support tables are expected to be added to the ARIA APG over time. The ARIA-AT group is in collaboration with the developers of the three most used screen readers: JAWS (Jobs Access with Speech), NVDA (NonVisual Desktop Access), and Apple Voiceover. The group is working on making a publicly available quarterly schedule for the entire APG.

Resting Not on Our Laurels

While the support tables are highly useful, they do not remove the need for regular screen reader testing. It is necessary to actively test content for conformance with the Web Content Accessibility Guidelines (WCAG).

When conducting screen reader tests, it is important for the tester to be an experienced AT user and versed in web accessibility. Regular testing not only ensures accessibility but also reduces the long-term costs of development and the probability of barriers affecting your audience.

Contribute to a More Accessible Future

If you wish to contribute to the APG Support Tables project, you can visit the W3C’s “Contributing to the ARIA and Assistive Technologies” wiki page. For specific ARIA issues or guidance in building a testing strategy for your content, feel free to send us a message to connect with an accessibility expert.

Tags: #WebAccessibility, #AssistiveTechnology, #ARIA, #WCAG

[Reference Link](!https://www.boia.org/blog/aria-team-announces-assistive-technology-support-tables)

David Moradi, CEO of AudioEye, shares insights on addressing digital accessibility.

The Challenges in Digital Accessibility

Statistically, only 3% of the internet is accessible currently. This effectively excludes 26% of American adults who live with a disability. As the CEO of AudioEye, a digital accessibility SaaS company, I have identified a correlation of two significant challenges that has deterred the widespread adoption of digital accessibility: the high cost involved and a complex legal framework.

Adopting a Technology-First Solution

Our findings indicate that the labor-intensive, manual process of identifying and remediating accessibility issues, which involves consultants and developers is not only expensive but also does not effectively address the magnitude of the problem. In response, we propose a combination of technology and human expertise, favoring a technology-first approach. Automation can assist in real-time monitoring and correction of most common accessibility errors, thereby significantly enhancing the browsing experience for those with disabilities. The remaining issues can then be addressed by human intervention which requires nuanced judgement.

The Complexity of the Internet

Approximately 250,000 sites are launched daily, many of which are designed without accessibility in mind. This lends to 97% of the internet being inaccessible. Maintaining accessibility even on websites designed with it in focus is an ongoing process fraught with challenges. Developers often work in time-bound ‘sprint cycles’ and may not have the luxury of time to address all accessibility errors before release. This showcased the necessity of a scalable solution to both remedy existing issues and provide ongoing monitoring for continuous accessibility.

The Cost of Accessibility Solutions

There is undeniable controversy surrounding the automation of accessibility solutions. The two prevalent models include inexpensive, automation-only solutions which are efficient in monitoring and detecting some, but not all issues; and costly manual services that provide site audits, reports and guidance for fixes. Neither model adequately addresses the an ability to monitor in real-time and fix issues at scale, while also being economically feasible for businesses of all sizes.

Legal Guidance and the Need for Clarity

Title III of the Americans with Disabilities Act (ADA) is often debated in terms of the definition of “places of public accommodation”. There currently exists ambiguity as to whether online stores are included, or whether it pertains only to businesses with physical and online stores. Recently, there has been guidance issued on web accessibility and the U.S. Department of Justice has announced plans to clarify and expand the reach of Title II of the ADA. A concrete legal directive with clear technical web accessibility standards would not only help businesses understand their legal standing, but also emphasize the government’s commitment to the rights of people with disabilities in the digital age.

It is my belief that a universally accessible internet can be achieved through the adoption of an affordable technology-first approach and a clear legal framework.

Forbes Technology Council
Do I qualify?

Tags: #digitalaccessibility, #ADA, #technologyfirst, #universalaccess
Reference Link

In the realm of digital communications, ensuring website accessibility or “a11y” has become pivotal. Beyond just ticking compliance checkboxes, a well-implemented accessibility strategy can reach more diverse audiences and offer a user-friendly experience.

Understanding Website Accessibility

Website accessibility refers to the practice of making your digital content and information technology inclusive and accessible to everyone. Broadly, categories that require consideration under digital accessibility are:

• Visual impairments
• Hearing impairments
• Learning, cognitive, and neurological impairments
• Physical and motor-control impairments
• Aging-related impairments

These can manifest in permanent, temporary, or situational forms. Consequently, building with accessibility in mind requires intent and strategy, because it won’t “happen” organically or accidentally.

Addressing Common Digital Accessibility Challenges

There’s a wide berth of issues that can arise while ensuring website accessibility, primarily due to the flexibility offered by various web design frameworks.

Sticking to Fully Conformant HTML

With several HTML standards existing in the digital sphere, adopting fully conformant HTML offers assistive technology optimal interaction opportunities. Over-reliance on additional languages like JavaScript might introduce more accessibility issues than solutions.

Considering RIA Attributes

ARIA (Accessible Rich Internet Applications) is a standard implemented in HTML to enhance the interaction of assistive technologies with website content. However, an overemphasis on these attributes might unintentionally impede accessibility efforts.

Addressing Perceivability Principles of Accessibility

Perceivability is one of the fundamental principles of accessibility. Websites are often perceived in a linear progression by those using assistive technologies. Understanding this can guide many design decisions, ensuring the site is accessible to all.

Addressing Color Contrast Accessibility

Color contrast is a common accessibility issue. While branding is vital, the site should remain perceivable for users with vision impairments. A balance between branding guidelines and accessibility principles should be a priority in the design process.

Developing a Practical Website Accessibility Strategy

Setting clear accessibility goals, project ownership, team equipping, and timing considerations are key to a successful strategy. Additionally, it’s essential to keep track of progress over time to understand the improvements being made and the points that need focus.

Implementing Accessibility Measures

1. Conducting a Website Accessibility Audit: An audit will help identify all existing accessibility issues and form a starting point for your remediation efforts.

2. Setting Up Website Monitoring Systems: Websites change frequently. A monitoring system would help detect new issues as they arise.

3. Embed Testing into Development Process: Accessibility testing should be included in the pre-release testing phase to ensure accessibility is not an afterthought but a requirement.

Conclusion

Website accessibility is not just a compliance requirement but a necessary strategy for providing a better user experience. By following practical strategies and making accessibility a core part of the development process, your website can become a more inclusive digital space.

---

Tags: #WebsiteAccessibility #DigitalInclusion #WebDevelopment #ContentAccessibility
Reference Link

By examining the general state of digital accessibility, we’re presented with a concerning insight. For five consecutive years, one web accessibility issue has held its top place – low-contrast text. Despite the known importance of this factor, it remains a significant barrier for users with visual impairments or color vision deficiencies. In this post, we will delve deeper into the underlying reasons for this persisting issue.

Understanding the State of Web Accessibility

Web Accessability In Mind (WebAIM) collects and analyzes annual data by conducting an automated audit of the home pages of the top 1 million websites. Although it’s important to note that automated tests may have limitations, they also provide us with a crucial snapshot of digital accessibility at large. The WebAIM’s Million report revealed a concerning fact – 96.3% of home pages had detectable WCAG 2.0 failures.

Dearth of Color Contrast

The most common issue was, unsurprisingly, the lack of proper color contrast. The report concluded that 83.6% of home pages used low-contrast text. That’s only a meager improvement of 0.3% from the previous year. So, despite widespread awareness, why does this issue continue to prevail?

Understanding the Importance of Contrast

According to an estimate by Georgetown University, an average of 8% of the U.S. population suffers from some sort of visual impairment. When text has inadequate contrast with the background, these users may find it challenging, if not impossible, to read the content. The difficulty is heightened for users with color vision deficiencies or low vision.

The Web Content Accessibility Guidelines (WCAG) defines a minimum color contrast ratio, derived from the difference in luminance between the foreground and background. Black text on a white background has the highest contrast ratio of 21:1. For most text, a minimum contrast ratio of 4.5:1 is required, and for larger text, a ratio of 3:1 is acceptable.

The Disconnect in Design

Even though WCAG’s color contrast rules are simple, most designers are either unaware of them or neglect them in favor of aesthetically complementary color pairs. However, such a lax mentality can result in legal repercussions, as color contrast issues feature prominently in accessibility lawsuits under the ADA.

Making Your Website Accessible

Identifying and rectifying color contrast issues is simple and quick. Automated tools can test color combinations against WCAG requirements. The Bureau of Internet Accessibility, for instance, offers a free a11y® color contrast accessibility validator, which can test web pages or individual color pairs.

Remember that optimized color contrast isn’t limited to text only. User interface components and essential graphic aspects too require a good color contrast ratio. A high-contrast mode can vastly improve accessibility, but all your webpage versions must maintain appropriate contrast.

Finally, ensure that all designers are educated about how color affects accessibility. Once your text color meets the necessary contrast ratio, you’re one step closer to a website that caters to the entire spectrum of its users.

Conclusion

To look out for all potential users of your website, sticking to the WCAG’s Level AA success criteria is a great way to ensure consistency. The free WCAG Level AA web analysis and the Ultimate Guide to Web Accessibility eBook can provide you with more essential accessibility information.

Tags: #webAccessibility #colorContrast #WCAG #webDesign

.
Reference Link

In this blog post, we unravel the complex nature of web accessibility. We delve into laundry lists of errors, intricacies of home page complexities, and offer an intimate knowledge of website standards.

Ground Rules and Methodology

Our evaluation targets various websites excluding those without home pages, pages that returned errors (404, etc.), pages with fewer than 10 HTML elements, and pages with more than 5,000 links to the same domain for SEO purposes.

Please be aware that the absence of detected errors does not necessarily indicate that a site is accessible or compliant.

Glaring Numbers: Detected Errors

Our evaluation flagged 49,991,225 distinct accessibility errors across one million home pages. That’s an average of 50.0 errors per page. Users with disabilities would expect to encounter errors on 1 in every 21 home page elements with which they engage.

Assessing Home Page Complexity

Home page elements have ballooned over 34% in the last 4 years. While detected errors saw a slight decrease, the increase in page complexity seems to dwarf these accessibility strides.

WCAG Conformance

Sadly,only about 20.7% of pages examined had 5 or fewer detected errors with 30.8% having 10 or fewer. WCAG failures mostly fell into a few categories such as low contrast text and missing alternative text for images.

WCAG Failure Table

| WCAG Failure Type | % of home pages in 2023 | % of home pages in 2022 | % of home pages in 2021 | % of home pages in 2020 | % of home pages in 2019 |
|——————|—————————|————————–|————————–|—————————|————————-|
| Low contrast text | 83.6% | 83.9% | 86.4% | 86.3% | 85.3% |
| Missing alternative text for images| 58.2% | 55.4% | 60.6% | 66.0% | 68.0% |
| Empty links | 50.1% | 49.7% | 51.3% | 59.9% | 58.1% |
| Missing form input labels | 45.9% | 46.1% | 54.4% | 53.8% | 52.8% |
| Empty buttons | 27.5% | 27.2% | 26.9% | 28.7% | 25.0% |
| Missing document language | 18.6% | 22.3% | 28.9% | 28.0% | 33.1% |

Fixing Just A Few Issues: A Game Changer

Experience shows that by addressing these common failures, we could significantly alter the accessibility landscape across the web.

Towards Better Automated Accessibility Testing

Despite a challenging field, brighter days are on the horizon. Our year-on-year automated accessibility tests are uncovering fewer violations, marking a progressive step towards global web accessibility improvement. However, we cannot rest on our laurels. Making all web content universally accessible is our end game.

Tags: #WebAccessibility #Errors #WCAG #HomePageComplexity

[ #complete ]
Reference Link