You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Size: The team was unanimous that the size for accessibility is xl.
Build Process: Accessibility is a major component in the design process for all products, services, devices and environments since all people are susceptible to any number of design concepts that could make their experience more difficult than others.
Sprint Need: The web is designed to work for all people regardless of their hardware, software, language, location or ability so by making accessibility a priority with our first sprint will help us create a high-quality website and not exclude people from using our product and service. By addressing the issue of accessibility first helps reduce time and cost by not having to solve for it right before our release.
Task branch name: Web_Accessibility
Brief statement of work performed: I added a link to the WebAIM Alternative Text guide in the footer for both admin’s and users to reference why uploading content or reviewing content uploaded by registered users.
Notes, comments, or update instructions: I don’t have any special notes or comments for my branch as I wanted to make it both simple and have it related to the topic of the issue, I created last week. As this is my first experience working with GitHub flow wanted to understand the process first before trying to add to much code.
The text was updated successfully, but these errors were encountered:
Issue Name: User Accessibility
User story available at: https://github.com/suwebdev/nifty-club/wiki/User-Story:-Accessibility.
Size: The team was unanimous that the size for accessibility is xl.
Build Process: Accessibility is a major component in the design process for all products, services, devices and environments since all people are susceptible to any number of design concepts that could make their experience more difficult than others.
Sprint Need: The web is designed to work for all people regardless of their hardware, software, language, location or ability so by making accessibility a priority with our first sprint will help us create a high-quality website and not exclude people from using our product and service. By addressing the issue of accessibility first helps reduce time and cost by not having to solve for it right before our release.
Task branch name: Web_Accessibility
Brief statement of work performed: I added a link to the WebAIM Alternative Text guide in the footer for both admin’s and users to reference why uploading content or reviewing content uploaded by registered users.
Notes, comments, or update instructions: I don’t have any special notes or comments for my branch as I wanted to make it both simple and have it related to the topic of the issue, I created last week. As this is my first experience working with GitHub flow wanted to understand the process first before trying to add to much code.
The text was updated successfully, but these errors were encountered: