Skip to content

Suggested changes for - Source, Benefits, Trade offs under each capability.  #17

Description

@UsableNet-WCAG

To move forward effectively around content and structure under capabilities , we could focus on organizing and detailing the capabilities we aim to make accessible, ensuring clarity on how they can be addressed both in-source and post-source. Here’s a refined explanation of our next steps:

1.	we have Identify Capabilities that need to be made accessible :
•	List the capabilities that require accessibility enhancements.

Under that we could change current lakes of Source, benefit , trade offs to the following

Effort and Resources for In-Source Correction:
• For each capability, describe the general approach needed to make it accessible within the source.

Post-Source Methods:
• Specify the post-source methods most suitable to rectify accessibility issues for each capability.

Trade-Offs Analysis:
• Compare the trade-offs between using post-source methods and addressing the issue in-source.
• Discuss the potential impact on performance, maintenance, and overall user experience.

Automat-ability - which we have now covered.

By structuring our approach in this manner, we can systematically address each capability, providing clear guidance on the effort required for in-source corrections, the post-source alternatives, and the implications of each method. This will ensure we help readers make informed decisions on the best approach for enhancing accessibility.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions