Features: A-Z Index
A
Administration Zone
B
Banners
C
Calendar
Catalogues
Chatrooms and IM
Community features
Content Sharing
Conversr Forums
Conversr Topic Polls
D
Design without barriers
Downloads
E
Ease of Use
eCommerce and Subscriptions
Extendable
F
Featured Content
G
Galleries
I
Installation
Integration
L
Localisation
M
Membership
N
News and Blogs
Newsletters
P
Parental Controls
Performance
Points
Privacy Tools
Q
Quizzes and Surveys
R
Rich Media
S
Search Engine Optimisation
Searching
Security
Spam Protection
Stay on Top
Structure / Navigation
Support Tickets
T
Template Programming Language
Testing tools
Themeing tools
Third party integration
W
Warnings / Moderation
Web Pages
Web standards
Website Polls
White-labeling (Debranding)
Wiki+
Newest 10 Entries
| Question | What are the current release plans for version 11? |
|---|---|
| Answer | As of July 22, 2024, we entered beta status where our focus is now smashing bugs and stabilising the software. All planned features have been implemented for 11.0 (and most others deferred to 11.1 or later), though we may still merge in a few minor features or tweaks. The upgrader has been tested on a typical non-custom v10 site. We will be releasing several beta versions in the beta phase. We do not know when we will be able to release the first Release Candidate or stable versions at this time. These plans are all subject to change without notice. |
| Question | Why is there a separate website for version 11? |
|---|---|
| Answer | That is explained in detail in this news article on compo.sr including the migration plans and implications. |
Top 10 Entries
| Question | What should I avoid doing in Composr to maintain accessibility? |
|---|---|
| Answer | Avoid using Comcode tags or other HTML elements that create dynamic effects in the user's browser, such as ticker and jumping. These can have a negative impact on navigation and scrolling. Provide alternate information for multimedia you upload so those with auditory impairments can still understand the content. Avoid creating multiple content items with the same title, as this can lead to accessibility issues and general user confusion. |
| Question | How does Composr handle forms for accessibility? |
|---|---|
| Answer | The web standards checker ensures that form labels are properly positioned and explicitly associated with their controls. It also checks that form elements have a logical tab order and are keyboard operable. |
| Question | How does Composr ensure accessible data tables? |
|---|---|
| Answer | The web standards checker enforces proper markup for data tables, including identifying row and column headers, and associating data cells with header cells. It ensures that tables are not used for layout (flex boxes and HTML grids are preferred for mobile responsiveness) unless they make sense when linearized. Composr provides summaries for tables to aid non-visual user agents in understanding their structure and content. |
| Question | How does Composr handle color contrast for accessibility? |
|---|---|
| Answer | Composr is designed with high graphic standards that aim to avoid poor color contrast in the default theme and Theme Wizard. But it is not perfect, especially for dark mode themes. Webmasters are still responsible for ensuring sufficient contrast in their own content and in custom themes. |
| Question | How do I provide text equivalents for images and multimedia in Composr? |
|---|---|
| Answer | Composr's web standards checker ensures that alternative text (using the "alt" attribute) is provided for images. It will warn if any images do not contain alt text. For multimedia, webmasters are responsible for providing captions and auditory descriptions either in the multimedia itself, on the description of the media, or uploaded as a caption file. |
| Question | How can I make sure my Composr website is accessible? |
|---|---|
| Answer | Enable the web standards checker in Composr while editing templates. Also do the same when previewing edited or new Comcode pages. Use the provided accessibility options in the Admin Zone to customize the webmaster experience according to your accessibility needs. Follow the webmaster concerns outlined in the "Helping improve site accessibility for disabled users" tutorial. Regularly test your website using third-party accessibility validation tools such as the WAVE Web Accessibility Evaluation Tool or the AChecker. |
| Question | What accessibility features are built into Composr? |
|---|---|
| Answer | Composr has an inbuilt web standards checker that helps ensure compliance with accessibility guidelines. Composr provides automatic sitemap generation functionality, a default sitemap page, and an advanced menu editor to manage navigation. Composr supports ARIA (Accessible Rich Internet Applications), which helps make dynamic content accessible. Composr includes options in the Admin Zone to fine-tune the webmaster experience for specific accessibility requirements. |
| Question | Does Composr comply with accessibility standards? |
|---|---|
| Answer | - Yes, Composr complies with the highest level of the WCAG (version 1.0 at the time of writing), level 3. - Composr also meets Section 508 guidelines, XHTML and CSS specifications, and the highest level of ATAG. - Composr conforms to these standards throughout, from user-facing screens to administrator interfaces. |
| Title | Extendable |
|---|---|
| Icon | |
| Description | Versatile: You can strip down to a core system, or build up with 3rd-party addons. Full API documentation High coding standards: No PHP notices. Type-strict codebase. MVC framework. Free online developer's guide book (in the tutorials) Custom field filters: For example, restrict news posts to a minimum length. Stack traces for easy debugging Synchronise data between staging and live sites using Resource-fs Breadcrumb overrides Advanced banning: Set your own banning rules for different hack attack codes. Even create your own ban pages (e.g. to mimic law enforcement bans for spammers). Code overrides: Implement modifications to the Composr code without directly editing the original code by creating _custom files. This makes upgrading much easier. Also supports contentious_overrides hooks and the override_api for more advanced overriding. Many different hook types allowing for modifying or extending Composr without modifying or overriding the code. |
| Title | Integration |
|---|---|
| Icon | |
| Description | Convert from other software: See our importing tutorial for a list of importers. Use an existing member system: See our download page for a list of forum drivers. Convert an HTML site into Composr pages LDAP support for corporate networks (Conversr only) HTTP authentication: Tie into an existing HTTP authentication-based login system (Conversr only) Proxying system: Programmers can integrate any existing scripts using our sophisticated proxying system (which includes full cookie support). Minimodules and miniblocks: Programmers can port existing PHP code into Composr itself without having to strictly conform it to Composr's framework |
