My Docs
DeploymentTrelloCalendar 🗓 Family Promise Roadmap
LAMBDA_LABS_Family_Promise
LAMBDA_LABS_Family_Promise
  • Home
  • navigation
    • Resume
    • My Notes:
    • NAVIGATION
    • Calendar
    • Youtube:
    • Roadmap:
    • TEAM MEMBERS
    • Running List Of Notes Links & Pertinent Info From Meetings
    • Trello
      • Github/Trello Integration
  • UX
    • UX_TOPICS
      • Action Items:
      • Accessibility
      • Figma Notes
        • Tables In Figma
        • Notes
        • Frames in Figma
        • Prototyping In Figma
        • More Notes
      • UX-Design
        • Facebook Graph API
      • Ant Design
        • ANT Components
          • Buttons
        • ANT DOCS
        • Application (Codesandbox)
      • Examples
      • How to add external URL links to your prototype
  • CANVAS
    • Interview
    • Design
      • What's Inclusive Design?
      • Accessibility
      • What are Design Systems?
    • Canvas
      • Career Readiness:
    • Notes
      • User Experience Design
      • User Research
      • Interaction Design
    • UX-Engineer
      • Accessibility
      • Patterns
      • Design Tools
      • UX Principles
      • Design Critiques
      • Product Review
      • Quiz
      • Seven Principles of Design
      • Other Articles
    • Labs
  • Front End
    • Frontend:
    • Redux
  • Back End
    • Backend:
      • API
  • Research
    • Research Navigation
      • Front End
      • Back End
      • UX
      • PTM
      • General
  • DS_API
    • Data Science API
  • ROLES
    • TEAM ROLES
      • Bryan Guner
  • Action Items
    • Trello
    • Maps
  • ARCHITECTURE
    • DNS
    • AWS
    • Heroku
  • Questions
    • From Previous Cohort
  • Standup Notes
    • Meeting Notes
      • Stakeholder Meeting 1
      • 9/29/2021
  • GitHub & Project Practice
    • GitHub
      • Github Guide
      • Github Actions:
      • Live Implementation
  • MISC
    • MISCELLANEOUS
      • Links
  • Background Information
    • Background Info
      • Swagger OPEN API SPECIFICATION
        • Swagger Docs (General)
      • GITHUB:
        • Git Bash
        • Git Prune:
  • DOCS
    • DS AP
    • What is JSON Web Token?
      • Environment Variables
      • Git Rebase:
      • Git Workflow:
      • Linting and Formatting
    • Project Docs
      • Eng-Docs-Home
      • Basic Node API
      • Contributing to this scaffold project
      • Examples:
    • PROJECT DESCRIPTION (Feature List)
    • Labs Learners Guide
    • REACT
      • Create React App
      • Awesome React
    • Labs Engineering Docs
      • Okta Basics
      • Roadmap
      • Repositories
  • Workflow
    • Workflow
    • Advice
  • AWS
    • AWS
      • Elastic Beanstalk
        • Elastic Beanstalk DNS
      • Amplify:
        • Amplify-DNS
    • Account Basics
    • AWS-Networking
  • Career & Job Hunt
    • Career
  • LABS
    • Introduction
    • User Stories
    • Why Pairing?
    • GitHub
    • Planning as an Engineer
    • Authentication and Authorization
      • Authentication VS Authorization
    • Giving Feedback
    • Modules Grades Understanding Your ISA
    • Rest Architecture
Powered by GitBook
On this page
  • What's Inclusive Design?
  • Designing Inclusively
  • Building Inclusively and Accessibly

Was this helpful?

  1. CANVAS
  2. UX-Engineer

Accessibility

PreviousUX-EngineerNextPatterns

Last updated 3 years ago

Was this helpful?

What's Inclusive Design?

Inclusive design is a philosophy that a product should be "accessible to, and usable by, as many people as reasonably possible ... without the need for special adaptation or specialized design" (, 2005).

In short, we shouldn't need to adapt products after the fact to handle certain "special" groups of users (e.g., those with visual impairments, those with low language or tech literacy). Instead, we should try to design our product, from the start, to accommodate them in a first-class way.

Designing Inclusively

Inclusive design doesn't mean we'll be able to design perfectly for every single person who might use our product. After all, it would be impossible to anticipate every possible way in with people might differ and in which their experience with a product might be affected.

Instead, we can only do our best to make an effort to understand the diversity of our potential users as we develop our product, and apply that understanding to our design.

We can then consciously incorporate different ways for users to interact with our product.

And then regardless, we should make it easy to adapt or extend our product for those we weren't initially able to design for.

For example, Microsoft's lays out three principles of inclusive design:

  • Recognize exclusion

  • Solve for one, extend to many

  • Learn from diversity

If we designed a product based on simply our own perspective and abilities, we'd be producing a product biased heavily toward people just like us. What about the rest? What factors might you consider?

Building Inclusively and Accessibly

As a designer, you also need to understand how your designs will be implemented. That means developing deep insight into how your product will be built.

As a UX designer, in some contexts, you might not write any code—you'll develop detailed processes and designs and hand them off to engineers. In other contexts, you might write a significant amount of code, bringing your designs to fruition largely by yourself. Regardless, if you're going to be working on a team, you'll need to set the vision and direction for how you'll design inclusively and build for usability—and work to ensure your design solutions are indeed achievable for a wide variety of users.

Here are some great resources to reference as you design and build products to ensure you're incorporating accessibility from the ground up:

for building accessibly on the web.

The W3C's are something you should reference throughout Labs to continuously audit your product's accessibility!

This compiles a long list of of ways to build accessible frontend components.

British Standards Institute (Links to an external site.)
resources on inclusive design (Links to an external site.)
W3C provides a wide variety of information and resources (Links to an external site.)
Web Contrast Accessibility Guidelines 2.0 (Links to an external site.)
article by Smashing Magazine (Links to an external site.)