Giter Site home page Giter Site logo

civicactions / accessibility Goto Github PK

View Code? Open in Web Editor NEW
27.0 43.0 11.0 24.14 MB

CivicActions Accessibility Site: A collection of resources about digital accessibility and how it aligns with open source, CivicTech and Digital Transformation.

Home Page: https://accessibility.civicactions.com

License: Other

HTML 11.53% Ruby 0.01% SCSS 29.40% JavaScript 58.93% Dockerfile 0.03% Shell 0.06% Python 0.04%
accessibility a11y civictech personas vpat digital-accessibility civicactions inclusion handbook guidebook government open-source documentation

accessibility's Introduction

Accessibility

This repository and website are the single source of truth for work on digital accessibility at CivicActions. This work is being done in the open because it is a best practice.

Working in the open allows us to

  • keep up with the work of other accessibility experts and engage with them;
  • share best practices we want to see widely adopted;
  • bring in other areas of our work that touch on accessibility;
  • embrace the journey of accessibility - being more accessible today than we were yesterday.

Another CivicActions site

This is not a duplication of content on hour homesite or our CivicActions Handbook Accessibility Section. Accessibility touches all aspects of an inclusive organization, so eventually we will have content about inclusion in our Distributed Government site.

This site is not a duplication, but an intentional and practical extension. As an example, all CivicActions employees are expected to be familiar with the material in the handbook, but not everyone needs to implement accessibility in their job.

Our Mission

Diversity equity and inclusion are key to any effective team, and CivicActions is no exception. Accessibility is a key part of this, as over 26% of Americans identify as having a disability. Our team is excited about finding new ways to build better products, and this includes removing barriers for people with disabilities.

CivicActions is an impact driven business that sees digital accessibility as something where we can make a positive difference. By working in the open with open source tools, we can not only improve our own work, but help shape how our industry grapples with this challenging issue. By working with governments and non-profit clients, we can ensure that our projects continue to improve over time.

Features

Most of our content is broken down into the Playbook and Guide. You can find out how to get involved or contact us through the site as well. You'll find updates of our projects in our News section and can find out who we are under People.

The meat and bones though is done through GitHub. Because we want to work in the public, you will be able to see some granular detail about our progress by looking at the issue queue. You may be checking out projects we're working on "behind the scenes" by looking at the code. That's great!

Contributing

We want your input. We need your help to make this resource better. Please visit the documentation page for how to contribute.

Related projects

Development

If you want to replicate this site, you are free to do so. It is a Jekyll site sitting on GitHub Pages. There are lots of resources that can help you learn how to fork this project and build on it.

Contacts

Email: [email protected]

CivicActions Slack: #accessibility

Licensing

At CivicActions we believe that releasing good work today helps us all produce great work tomorrow. By regularly shipping the work and making it open we can help build a vibrant, inclusive ecosystem. To help build community around these ideas, we have released this repository under a Creative Commons Attribution-ShareAlike 4.0 International Public License.

accessibility's People

Contributors

adamchaboryk avatar adriancooke avatar cheapwebmonkey avatar danid123 avatar dependabot[bot] avatar dmundra avatar grugnog avatar jerseycheese avatar jhoude5 avatar laflannery avatar lukefretwell avatar melindaburgess avatar mgifford avatar mikang avatar niradatta1 avatar niradatta1-zz avatar pre-commit-ci[bot] avatar shaal avatar sharjeelaziz avatar shawnthompson avatar vanessaluxen avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

accessibility's Issues

Set up sprint planning + check-in times

We're going to set up a 30-minute weekly (Mon.) sprint planning call and twice-weekly (Tues./Thurs.) 15-minute scrum.

Anyone interested in joining either of these?

To-do

  • Ask team members if they'd like to join
  • Add to CivicActions Accessibility calendar / invite team members
  • Tie notification into Slack

Collect resources distributed teams & accessibility

Integrate accessibility into existing teams

Define the CivicActions approach to accessibility - open & agile

Highlight How the CA Design Process Embraces Accessibility

We need more clarity about how accessibility fits into

  • Customer/Citizen Experience (CX) and/or
  • UX and/or Human Centred Design (HCD)
  • Wireframes

To-do

  • Create initial document (linked below)
  • Research accessibility personas (Nira)
  • Research plain language guides (Nira)
  • Research wireframe annotation (Michelle)
  • Research accessibility checklists (Michelle)
  • Meet to discuss findings and progress
  • Meet to propose a design process with accessibility baked in every step of the way
  • Decide whether this should be a blog post or microsite
  • Publish!

Doc

https://docs.google.com/document/d/1rFb1sYwSYBicRlz1CU_hEWQRV8v-t_UJ-rp1ZKfqPSI/edit?usp=sharing

Potential clarification for Drupal issue 3048785 in VPAT

Not sure if this detail is something that gets added to VPAT, but the phrasing "There are places where we are seeking to improve the focus for authors and administrators" does make it seem like it's an overall issue with Drupal, when it's something specific to an IE bug. The IE bug is: element styled as display: flex will receive focus on click. This is not specific to Drupal.

The reason that issue 3048785 exists is because Claro's is committed to making all focus states visible. The IE11 bug focuses elements that really shouldn't be focusable, but Claro is going to make that focus state visible regardless.

Create Machine Readable VPAT Format

If we are going to have a machine readable VPAT we need to have a clear distinction between data & presentation.

There are examples of this with GitHub:
https://github.com/github/government.github.com/edit/gh-pages/docs/accessibility.md

GitLab looks good (and is probably a better VPAT), but is just HTML
https://design.gitlab.com/accessibility/vpat/

@benbalter also has an example:
https://github.com/benbalter/jekyll-accessibility-template/blob/master/_data/accessibility.yml

One of the important things about a machine readable version of a VPAT is that it must also be human readable. It should be easy for someone to review the code and understand without looking at the final expression in HTML. Use of comments is probably the best way to do this.

Write-up yml + VPAT + CaC

Let's discuss/document/socialize how .yml files can streamline the VPAT creation and also be incorporated into the Compliance as Code process.

Post

Work in progress: https://docs.google.com/document/d/1XvSdZn6Q2mnvcVUnoB-Yxsn8IgzzPjLmoqlCkr5Sdgw/edit?usp=sharing

Notes

"“Voluntary Product Accessibility Template” and “VPAT,” including the template format, are Federally Registered Service Marks of the Information Technology Industry Council (ITI). VPAT users agree not to deviate materially from the template format providedby ITI, and to use the service mark (“®”) where appropriate."

References

cc @mgifford @grugnog

Accessibility Events

  • Add to CA Accessibility Site
  • Add to CivicActions Accessibility calendar
  • Incorporate into CivicActions marketing/outreach efforts (blog, social)
  • Think about how we want to participate in these events

Create accessibility training program for CivicActions team members

@elizabethraley, @mgifford and I are talking about developing a high-level accessibility training (30-60 minutes) for CivicActions team members. We'd like to test on groups of current employees and then do monthly for new employees.

Who's the best person to talk with about this?

Audience

CivicActions team members (and eventually clients)

Objective

To educate CivicActions team members on web accessibility and the importance of this in our work with government.

Key results

  • 100% of CivicActions team members attend digital accessibility training.
  • All CivicActions team members score 90% or higher on a digital accessibility quiz.
  • 100% of CivicActions team members are using appropriate accessibility tools.

Working Documents

To-do

  • Talk with ops
  • Onboarding deck
  • Reach out to Kylea for integration
  • Run through with existing staff
  • Run through with live "onboardees"
  • Write blog post

Create web-based presence

Per chat with @mgifford, consider building a simple web-based presence to house the practice area work so that it's more accessible to others.

Including:

  • OKRs
  • Onboarding on Accessibility
  • Test
  • Practice Area Site
  • Point of contact - Slack/Email
  • Guide - Documentation
  • How we work - Project Board
  • People - The team
  • Calendar
  • Roadmap (Milestones)

Set up CivicActions Accessibility Newsletter

Drupal issue 2766853 is not an accessibility bug

See comment #4 and #28 for more information.
The input they reference is already accessible. The person that filed the issue wanted to change how the input communicates itself to AT (a title attribute) to a label. They wanted to add a label element so they could use CSS with pseudo-selectors, there were no accessibility problems reported or discovered.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.