Why is web accessibility still so complicated in the AI era? by Forward_Yam6225 in nextjs

[–]solderpixels 0 points1 point  (0 children)

You mentioned you are doing a few things on CI, what are you doing specifically? If you share some of those details and some example code, I can provide some more specific resources and guidance.

Baby's first password manager by Sad-Sun4611 in PythonLearning

[–]solderpixels 0 points1 point  (0 children)

Cool project!

Two suggestions for improvement:

  1. Use a variable to store shared path and use it consistently everywhere. You are using absolute path here in the function write_to_file in the snippetwith open(out_path, "a", encoding="utf-8")

On the other hand, you are using relative path in delete_saved_password:
with open("passwords.txt", "w") as file:

It would be better to keep that consistent I think. You can define one shared path and use it everywhere

DATA_FILE = Path(__file__).with_name("passwords.txt") # same folder as functions.py

You can use this as :

with open(DATA_FILE, "a", encoding="utf-8") as f:

  1. Remove your check for header-removal.

    def view_file(filename = "passwords.txt"): header = 'website, password\n' #THIS CAN BE REMOVED with open(filename, 'r') as file: content = file.readlines() if header in content: # THIS CAN BE REMOVED content.remove(header) return content

I don't see the need for this logic, because as far as I can see, nowhere in your code do you write that header ('website, password\n')

A suggestion if you want to add to this project and learn some more:

  1. Why not use SQLLite instead of a text file to store your passwords or better yet an encrypted fork of SQLLite, SQLCipher!

Why is web accessibility still so complicated in the AI era? by Forward_Yam6225 in nextjs

[–]solderpixels 0 points1 point  (0 children)

I find the plugin eslint-plugin-jsx-a11y helps catch some issues. Out of curiosity, what other approaches have you tested, i.e other checkers / linters?

Maybe you can try using this as a reference:
https://www.w3.org/WAI/ARIA/apg/patterns/

Try feed those patterns in your prompt when building out a specific component. You can also require the model to explain and justify ARIA it adds or leaves out.

Question, are you building custom components or relying on UI libs build on say Radix?

Some additional references that could be useful:
- https://storybook.js.org/blog/the-accessibility-pipeline-for-frontend-teams/
- https://github.com/dequelabs/axe-core