wesleybranton/cash-counter

Effortlessly count your cash without complex math.

cash-counter's Issues

Collect feedback on uninstall

When a user uninstalls the add-on, they should be asked to complete an optional feedback survey in a new tab. This will help to find issues or areas where the add-on could improve.

Change options UI to New Browser Style library

Change the options UI so that it uses the standard New Browser Style library, like the other add-ons I have released.

Change add-on branding to appear flat

Consider changing the add-on branding icon to a flat design, which is more modern looking and may display nicer on the browser toolbar.

Collect general feedback

User should be able to send feedback about the add-on at any time. This will help to detect issues with the add-on or potential improvements that can be made.

Add support for localization

The add-on can easily be set up to support i18n. Although the add-on is unlikely to be translated any time in the foreseeable future, it can be if someone is willing to.

Allow users to add currency values

To actually fully support non-dollar currency, users need to be able to add/remove rows to the cash counter table and have full control over which rows have a coin roll counter visible.

This will also required a change to the ID system used in the settings to support face values that have more than 3 digits (excluding the decimal). The highest value supported by the "d#####" ID syntax is $999.99. The number of digits will need to be increased.

As there are not currently any non-dollar currency users, this change is low priority.

Update for WCAG 2.2 compliance

In an effort to make the content of the internet more accessible to everyone, all of my repositories will be reviewed to ensure that they fulfil the WCAG 2.2 requirements. This will take time. The current goal is to make all projects comply with level AA, including as many level AAA standards as possible.

Items that are bold are new to WCAG 2.2. Items that do not apply to the project will be marked as completed and marked with a strikethrough.

Guideline 1.1 – Text Alternatives

• 1.1.1 - Non-text Content (A)

Guideline 1.2 – Time-based Media

• 1.2.1 - Audio-only and Video-only (Prerecorded) (A)
• 1.2.2 - Captions (Prerecorded) (A)
• 1.2.3 - Audio Description or Media Alternative (Prerecorded) (A)
• 1.2.4 - Captions (Live) (AA)
• 1.2.5 - Audio Description (Prerecorded) (AA)
• 1.2.6 - Sign Language (Prerecorded) (AAA)
• 1.2.7 - Extended Audio Description (Prerecorded) (AAA)
• 1.2.8 - Media Alternative (Prerecorded) (AAA)
• 1.2.9 - Audio-only (Live) (AAA)

Guideline 1.3 – Adaptable

• 1.3.1 - Info and Relationships (A)
• 1.3.2 - Meaningful Sequence (A)
• 1.3.3 - Sensory Characteristics (A)
• 1.3.4 - Orientation (AA)
• 1.3.5 - Identify Input Purpose (AA)
• 1.3.6 - Identify Purpose (AAA)

Guideline 1.4 – Distinguishable

• 1.4.1 - Use of Color (A)
• 1.4.2 - Audio Control (A)
• 1.4.3 - Contrast (Minimum) (AA)
• 1.4.4 - Resize text (AA)
• 1.4.5 - Images of Text (AA)
• 1.4.6 - Contrast (Enhanced) (AAA)
• 1.4.7 - Low or No Background Audio (AAA)
• 1.4.8 - Visual Presentation (AAA)
• 1.4.9 - Images of Text (No Exception) (AAA)
• 1.4.10 - Reflow (AA)
• 1.4.11 - Non-text Contrast (AA)
• 1.4.12 - Text Spacing (AA)
• 1.4.13 - Content on Hover or Focus (AA)

Guideline 2.1 – Keyboard Accessible

• 2.1.1 - Keyboard (A)
• 2.1.2 - No Keyboard Trap (A)
• 2.1.3 - Keyboard (No Exception) (AAA)
• 2.1.4 - Character Key Shortcuts (A)

Guideline 2.2 – Enough Time

• 2.2.1 - Timing Adjustable (A)
• 2.2.2 - Pause, Stop, Hide (A)
• 2.2.3 - No Timing (AAA)
• 2.2.4 - Interruptions (AAA)
• 2.2.5 - Re-authenticating (AAA)
• 2.2.6 - Timeouts (AAA)

Guideline 2.3 – Seizures and Physical Reactions

• 2.3.1 - Three Flashes or Below Threshold (A)
• 2.3.2 - Three Flashes (AAA)
• 2.3.3 - Animation from Interactions (AAA)

Guideline 2.4 – Navigable

• 2.4.1 - Bypass Blocks (A)
• 2.4.2 - Page Titled (A)
• 2.4.3 - Focus Order (A)
• 2.4.4 - Link Purpose (In Context) (A)
• 2.4.5 - Multiple Ways (AA)
• 2.4.6 - Headings and Labels (AA)
• 2.4.7 - Focus Visible (AA)
• 2.4.8 - Location (AAA)
• 2.4.9 - Link Purpose (Link Only) (AAA)
• 2.4.10 - Section Headings (AAA)
• 2.4.11- Focus Appearance (Minimum) (AA)
• 2.4.12 - Focus Appearance (Enhanced) (AAA)
• 2.4.13 - Fixed Reference Points (A)

Guideline 2.5 – Input Modalities

• 2.5.1 - Pointer Gestures (A)
• 2.5.2 - Pointer Cancellation (A)
• 2.5.3 - Label in Name (A)
• 2.5.4 - Motion Actuation (A)
• 2.5.5 - Target Size (AAA)
• 2.5.6 - Concurrent Input Mechanisms (AAA)
• 2.5.7 - Dragging (AA)
• 2.5.8 - Pointer Target Spacing (AA)

Guideline 3.1 – Readable

• 3.1.1 - Language of Page (A)
• 3.1.2 - Language of Parts (AA)
• 3.1.3 - Unusual Words (AAA)
• 3.1.4 - Abbreviations (AAA)
• 3.1.5 - Reading Level (AAA)
• 3.1.6 - Pronunciation (AAA)

Guideline 3.2 – Predictable

• 3.2.1 - On Focus (A)
• 3.2.2 - On Input (A)
• 3.2.3 - Consistent Navigation (AA)
• 3.2.4 - Consistent Identification (AA)
• 3.2.5 - Change on Request (AAA)
• 3.2.6 - Findable Help (A)
• 3.2.7 - Hidden Controls (AA)

Guideline 3.3 – Input Assistance

• 3.3.1 - Error Identification (A)
• 3.3.2 - Labels or Instructions (A)
• 3.3.3 - Error Suggestion (AA)
• 3.3.4 - Error Prevention (Legal, Financial, Data) (AA)
• 3.3.5 - Help (AAA)
• 3.3.6 - Error Prevention (All) (AAA)
• 3.3.7 - Accessible Authentication (A)
• 3.3.8 - Redundant Entry (A)

Guideline 4.1 – Compatible

• 4.1.1 - Parsing (A)
• 4.1.2 - Name, Role, Value (A)
• 4.1.3 - Status Messages (A)

Change add-on appearance to flat

The overall appearance of the add-on should be changed to give the add-on a more flat and modern appearance.

Add support for other currency

Currently, the add-on only supports $ currencies. A setting should be added to allow the user to set the currency symbol.

AMO listing compatibility issue

The extension cannot be downloaded from AMO to anything other than a Windows computer. This is because the extension was last updated when AMO still segregated Windows, Mac and Linux.

An update needs to be pushed to the listing to update the compatibility to any of the Firefox for Desktop platforms.

Make compatible for Android

There's nothing in this add-on that should cause issues with Firefox for Android. The necessary UI upgrades should be made to enhance the Firefox for Android experience and the AMO listing should be compatible with Android.