For example ...

In various operations, the HTML view is mushed together unless we first add an innocuous space (or something), save and reopen. How long would it take to fix that bug?

In the opt-out macro, the only acceptable syntax is {Unsubscribe_Url}, exactly like that. Anything else (e.g., "URL" or a space instead of an underscore), and the link won't work. Worse, your system will put an unsightly "HEY CLICK ME" invitation to opt-out at the email's bottom. How long would it take to correct your examples (and make their syntax uniform) and make the macro case-insensitive? (I suggest also accepting either a space or an underscore, as various macros have both forms, and you'll need to make them backwards-compatible.)

I could round up more examples, but surely Support has a list. I'd think fixing such glitches would save us all (including Support) a lot of time, as well as improve usability, user confidence, and even moral.

We have hit a road-block with our credit union.
As we were attempting to set up online payment so that members cold pay directly from the Credit Union (vs. using PayPal), our CU informed us that we need an account # on the invoice.
When we are creating the invoice, it shows the user along with their user ID#
However, when the actual invoice is created, the system drops their ID # and only shows their name.
If we could have this ID# printed automatically on the invoice as their Account number, then this would satisfy the requirements to having our club added to the CU as a list of Payees.

Would like to request accessibility features to be added to the site's templates including:

FORMS:

Add label tags around the form's labels, and associate the labels with their form fields using IDs (explanation: http://webaim.org/techniques/forms/screen_reader.php#labels)

Group form controls using fieldsets and legends, where appropriate (explanation: http://webaim.org/techniques/forms/screen_reader.php#group).

NAVIGATION:

Add a "skip navigation feature" to allow keyboard users to skip over the navigation menus, when they are tabbing thru links on a page. (explanation: http://webaim.org/techniques/skipnav/#focus).

These features would make the sites more accessible to disabled users (people who cannot use mouse, blind people using screenreader software, etc) and help make them more compliant with the US government's Section 508 guidelines.

Please give more robust Search Engine Optimization capability to those of us who know its importance and know how to use it.

It's more than "SEO"; it's a matter of site functionality.

We get a lot of visitors from search engines. Often they find and go directly to an event description page, or the overall list of events, where they register and have are not even aware that they should know more about us first. For this reason, and for SEO reasons, we would benefit greatly if we were able to tweak the displayed page title and search snippet for EACH event description. Otherwise, Google picks up fragments of text containing the search words, which is usually does not help convert to a clickthrough, and does not help us explain what they've found.

I believe HTML 5 allows meta tags to be contained in the body of a page (rather than in the header), but it requires a certain specification in the header. I am unfamiliar with the required code and syntax, but surely someone at WA is. However WA's HTML editor immediately deletes any meta tag in the event description, unless it is contained in an HTML comment tag, which will probably make it ignored, or worse, look like spamming. So that needs attention from WA, too.

Please rocognize that a Title tag, a page Headline (e.g., H1), and the title of an event as shown in the master events list are NOT the same things (and for that matter, neither is the page's file name, which we cannot customize for an event, either, right?). Each serves a different purpose and needs to be worded specifically for that. The title that appears in a SERP would look stupid, wordy and redundant in a list of events, and would not be an attractive headline. It might contain stop words and punctuation and would often be relatively long, so it would not be good as a custom URL, either.

In summary, each event description (and similar generated pages) needs the following fields, which can contain defaults but need to be individually customizeable for that particular event:

* Custom URL (file name, for that particular event)
* Title tag (for that particular event). Field length should match Google's typical minimum (although actually Google goes by the space used, not character count, so allow a bit extra).
* Meta Description tag (for that particular event) (ditto regarding field length)
* "List" title (appears on the list of all events and as the Title macro in emails)
* Headline for the description text (an existing capability)

This is mainly about Google but of course all major search engines are relevant. And this is all standard SEO/marketing best practices, nothing "black hat" about it.

Our community organization maintains a lot of short legal PDF documents for reference by our members. The current website we use has a document library function which makes it easy to load a lot of documents into a web page. This page then lists their titles, when they were added, how many hits each document has had over time, etc. You can also sort and resort the documents by clicking on the various column headings.

Right now, we have to manually insert details about each document into a static HTML table. Keeping the documents properly sorted is also difficult. If WA were to offer this type of Functional Page, the folks responsible for maintaining the document library would be much more enthusiatic about the migration. Thanks!

When any member who has been granted any level of admin rights logs in, they have the option to switch into 'Admin view' by clicking the 'Admin view' button at the top right of their screen. Once in Admin view they see a button labeled 'Public view' at the top of their screen - but since they are already logged in clicking that button will not give them a 'Public view' - rather they would have 'Regular view' which will still display content to them that the public does not see. To have a Public view, they must log out. This is confusing to our admins who think they have checked functionality 'as though they were the public' when in fact they have only checked what appears for a user with Admin rights.

Can you relabel the 'Public view' button to 'Regular view' ?

When our Members register for events, for them to receive Member rates, they must use the email address associated with their Member profile in Wild Apricot; however, these Members often register delegates within their organization who have a different email address. By doing so, the delegates will still receive Member rates. These delegates do not have access to check the emails sent to the organization's log-in email. So, to email delegates before, during and after events, I have to export the delegates list and send emails through Outlook. Please create a system in which organizations can get Member rates for events, register their staff with a different email address, and their staff will be able to receive emails directly from Wild Apricot.

Thank you!

Rather than worry about specific, discrete pieces of functionality, I'd propose an overhaul of the entire user experience including:
1) Make reports that are more useful, e.g. new members, lapsed members, invomplete registrations
2) Overhaul the email workflwo, e.g. you should be able to name an email before step three in the process
3) A complete overhaul of the event setup and pricing elements. e.g. Having to create a registration form is a nightmare. Why aren't there simple templates and an ability to preview a form without having to log in as a user?

With all due thanks, and respect, pleasing the 5% of power users who are asking (demanding) specific pieces of functionality is a waste of time when 90% of the users can't get through the basics because an overall design and UI that are clearly from the late 1990's early 2000's.

I hope the above is both constructive and helpful. I do appreciate the work that goes into WA, and offer it to help. Kind regards--Jim

I like being able to send email to our list of members, and I like being able to have them maintain their own contact info via their profile.

I hate your email/HTML editing tool, it's just horrible.

Can you please give me a way to simply have an email list address to which I can send an email from my favorite email client and it will forward to the membership list? I don't really care about link or open tracking.

Example: send an email to members@mydomain.com. It forwards to all members (or whatever search subset I define when I create the email name "members") anything I send to it.

Actually, after thought, I'd probably need to send it to "members@mydomain.wildapricot.com" or something since you are not my email provider by default, but I'd be fine with that.

Simple to use.

Thanks.